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.
PostgreSQL Experts Inc.
pgsql-hackers by date
|Next:||From: Andrew Dunstan||Date: 2013-02-01 01:05:43|
|Subject: parameter info?|
|Previous:||From: Josh Berkus||Date: 2013-02-01 01:01:33|
|Subject: Re: Cascading replication: should we detect/prevent cycles?|