Hi, if pg_rewind is told to fetch data via a libpq connection (--source-server), synchronous replication is enabled and there is only one sync standby (pilot error, but sill); pg_rewinding the old master hangs at the CREATE TEMPORARY TABLE step (CREATE TABLE waiting for X/XXXXXXXX). At least this happened to one of our clients while evaluating pg_rewind.
To the user, the last thing printed is "need to copy XXXX MB [...]". If the user cancels the pg_rewind command with ^C, the backend keeps hanging around even in --dry-run mode. That won't hurt too much as it does not seem to block future pg_rewind runs after synchronous_commit has been set to a different value, but looks surprising to me. Not sure whether pg_rewind could error out gracefully without hanging in this case, but maybe it could/should clean up the query on SIGTERM? And at the least, maybe this caveat should be documented? Michael -- Michael Banck Projektleiter / Senior Berater Tel.: +49 2166 9901-171 Fax: +49 2166 9901-100 Email: michael.ba...@credativ.de credativ GmbH, HRB Mönchengladbach 12080 USt-ID-Nummer: DE204566209 Trompeterallee 108, 41189 Mönchengladbach Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers