Heikki,
I ran into an unexpected issue while testing. I just wanted to fire up
a chain of 5 replicas to see if I could connect them in a loop.
However, I ran into a weird issue when starting up "r3": it refused to
come out of "the database is starting up" mode until I did a write on
the master. Then it came up fine.
master-->r1-->r2-->r3-->r4
I tried doing the full replication sequence (basebackup, startup, test)
with it twice and got the exact same results each time.
This is very strange because I did not encounter the same issues with r2
or r4. Nor have I seen this before in my tests.
I'm also seeing Thom's spurious error message now. Each of r2, r3 and
r4 have the following message once in their logs:
LOG: database system was interrupted while in recovery at log time
2012-12-19 02:49:34 GMT
HINT: If this has occurred more than once some data might be corrupted
and you might need to choose an earlier recovery target.
This message doesn't seem to signify anything.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
