On 2017-05-27 19:48:24 +0300, Vladimir Borodin wrote: > Well, actually clean shutdown of master with exit code 0 from `pg_ctl > stop -m fast` guarantees that all WAL has been replicated to standby.
It does not. It makes it likely, but the connection to the standby could be not up just then, you could run into walsender timeout, and a bunch of other scenarios. > But just in case we also check that "Latest checkpoint's REDO > location" from control file on old master after shutdown is less than > pg_last_xlog_replay_location() on standby to be promoted. The *redo* location? Or the checkpoint location itself? Because the latter is what needs to be *equal* than the replay location not less than. Normally there won't be other records inbetween, but that's not guaranteed. > And if something would go wrong in above logic, postgres will not let you > attach old master as a standby of new master. So it is highly probable not a > setup problem. There's no such guarantee. There's a bunch of checks that'll somewhat likely trigger, but nothing more than that. - Andres -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
