Currently the command `docker-compose build` throws an error for building the database because it uses an old pip version.
This PR updates pip right before it is called. Anyways this should just be a temporary fix because the image uses Python 2.7 wich out of support since Jan 2020
I tried to use wal-e as mentioned on dockerhub (see https://hub.docker.com/r/mattermost/mattermost-prod-db). To do the base backup I had to do some additional steps (see https://github.com/mattermost/mattermost-docker/issues/346):
- mount a volume into the database docker container (path in the container is /etc/wal-e.d/env) and put all credentials and the s3 prefix to this folder
- exec into the container and create a superuser (Command: CREATE USER postgres SUPERUSER;)
Now it still fails with the message, that the package *pv* is missing
WAL logs in archive mode will consume a lot more spaces and not useful
when backup is off. This fix add ability to switch WAL logs mode based
on the backup switch.
You may see this error if you use pgsql 9.5 with 9.4 data.
> FATAL: database files are incompatible with server
> DETAIL: The data directory was initialized by PostgreSQL version 9.4, which is not compatible with this version 9.5.0.
