Issues with putting dockerized Postgres OLTP database in read only

I have a dockerized postgres 9.3.5 OLTP instance that I’m going to update to 9.5.2. Instead of shutting it down and doing a pg_dumpal to a file and then load it I would like to spin up a new docker container and pipe the database pg_dumpall -h localhost -p [port] -U postgres | psql -h localhost -U postgres -p [port]. I’m thinking I could alter the postgresql.conf to be in read only mode. This would temporarily mess with my app but at least users could still SELECT. Is there a better way to go about this? Are there any big issues with putting in read only mode while I pipe the database over?

  • Tutum HAProxy Docker Virtual Host forward to entry point path
  • docker-compose up fails with “UnixHTTPConnectionPool(host='localhost', port=None): Pool is closed”
  • Ports On Docker
  • Mount docker volume subfolders
  • Angular 2 build once, deploy anywhere
  • how can i launch the kafka scheduler using marathon in minimesos?
  • Using GitLab CI with the Python 'onbuild' image, the packages in requirements.txt don't seem to get installed
  • Docker, postgres. Port is already allocated
  • Docker Toolbox - hang on `docker push`
  • Prometheus with multi-container pod on kubernetes
  • How to mount file from host to docker container on ECS
  • Node http-proxy in Docker container
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.