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?

  • List used images from Docker Compose
  • persist and share data from docker mongo container (with docker)
  • No matching server found with minimum required memory for the node [AppServer] on DCHQ
  • How to build a sidecar container for passing files from a machine outside of the Kubernetes cluster?
  • How to move Postresql to RAM disk in Docker?
  • dial unix /var/run/docker.sock: no such file or directory after upgrading to lxc-docker
  • How to run etcd cluster in docker using ansible?
  • Providing a stable url to access a docker container from another docker container
  • Receive UDP Multicast in Docker Container
  • - Connecting to MySQL with Scala
  • Kubectl run using yaml file config
  • Docker Hub Login Without Password
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.