mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-08-31 08:27:23 +02:00
If you point pg_rewind to a server that is using synchronous replication, with "pg_rewind --source-server=...", and the replication is not working for some reason, pg_rewind will get stuck because it creates a temporary table, which needs to be replicated. You could call broken replication a pilot error, but pg_rewind is often used in special circumstances, when there are changes to the replication setup. We don't do any "real" updates, and we don't care about fsyncing or replicating the operations on the temporary tables, so fix that by setting synchronous_commit off. Michael Banck, Michael Paquier. Backpatch to 9.5, where pg_rewind was introduced. Discussion: <20161005143938.GA12247@nighthawk.caipicrew.dd-dns.de> |
||
---|---|---|
.. | ||
initdb | ||
pg_archivecleanup | ||
pg_basebackup | ||
pg_config | ||
pg_controldata | ||
pg_ctl | ||
pg_dump | ||
pg_resetxlog | ||
pg_rewind | ||
pg_test_fsync | ||
pg_test_timing | ||
pg_upgrade | ||
pg_xlogdump | ||
pgbench | ||
pgevent | ||
psql | ||
scripts | ||
Makefile |