On 01.02.2013 02:04, Josh Berkus wrote:
I thought this was only a 9.3 issue, but it turns out to be
reproduceable on 9.2.2. Basically, I did:
1. master is queicent ... no writes occuring.
2. createded cascading replica (reprep1) from replica (repmaster)
3. reprep1 remains "in recovery mode" until a write occurs on master
I've been able to reproduce this several times on my laptop using
postmasters running on different ports.
Hmm, that sounds like the issue discussed here:
http://www.postgresql.org/message-id/50c7612e.5060...@vmware.com, and
fixed by this commit:
http://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=fb565f8c9616ec8ab1b5176d16f310725e581e6e
Can you check if you still see that behavior with REL9_2_STABLE?
- Heikki
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
