Just for the records, I use this solution now:
https://dba.stackexchange.com/questions/186045/how-do-i-prevent-changes-to-my-database/186051#186051
Change the port of PostgreSQL on prod-server-old. This way it is unlikely that clients connect to the DB during
pg_dumpall --port=OTHER_PORT
BTW:
Just for the records, I asked here the same question and got some replies:
https://dba.stackexchange.com/questions/186045/how-do-i-prevent-changes-to-my-database
Am 11.09.2017 um 15:25 schrieb Thomas Güttler:
I did a stupid mistake. I run the final pg_dumpall without switching to
single-user-m
I did a stupid mistake. I run the final pg_dumpall without switching to
single-user-mode first.
With "final" I mean that the dump should be transferred to a different machine.
After the dump
the old machine was shut down forever.
My mistake was that I stopped the services, but one process was
