On 01/06/2015 05:17 PM, Andres Freund wrote: > A real solution to this requires more. You need to 1) disable writing > any wal 2) force catchup of all possible standbys, including apply. Most > importantly of the new master. This requires knowing which standbys > exist. 3) promote new master. 4) only now allow reconnect
That can all be handled externally to PostgreSQL. However, as long as we have a recovery.conf file which only gets read at server start, and at no other time, no external solution is possible. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
