Heikki, The next time I get the issue, and I'm not paying for 5 cloud servers by the hour, I'll give you a login.
--Josh ----- Original Message ----- > On 19.12.2012 17:27, Heikki Linnakangas wrote: > > On 19.12.2012 15:55, Heikki Linnakangas wrote: > >> On 19.12.2012 04:57, Josh Berkus wrote: > >>> 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. > >> > >> Ok.. I'm going to need some more details on how to reproduce this, > >> I'm > >> not seeing that when I set up four standbys. > > > > Ok, I managed to reproduce this now. > > Hmph, no I didn't, I replied to wrong email. The problem I managed to > reproduce was the one where you get "requested WAL > segment 000000020000000000000003 has already been removed" errors, > reported by Thom. > > - Heikki > -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers