On 2013-11-21 12:51:17 -0800, Josh Berkus wrote: > On 11/21/2013 12:46 PM, Andres Freund wrote: > > No. Check > > http://archives.postgresql.org/message-id/20131120234141.GI18801%40awork2.anarazel.de > > > > The problem is starting with hot_standby=on on a system with > > recovery.conf present. It is independent of whether you use streaming > > replication, archive based recovery, or just shutdown the server and > > manually copy xlog segments there. > > As long as hot_standby=on, and recovery.conf is present you can hit the > > bug. > > Oh, aha. There have to be some transactions which are awaiting > checkpoint, though, correct? As in, if there's no activity on the > master, you can't trigger the bug?
Correct. Also, if you *start* at such a checkpoint you're not vulnerable until the standby is restarted. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
