Heikki, > The problem goes away after some time, after the 1st standby has > streamed the contents of 000000020000000000000003 and written it to > disk, and the cascaded standby reconnects. But it would be nice to > avoid > that situation. I'm not sure how to do that yet, we might need to > track > the timeline we're currently receiving/sending more carefully. Or > perhaps we need to copy the previous WAL segment to the new name when > switching recovery target timeline, like we do when a server is > promoted. I'll try to come up with something...
Would it be accurate to say that this issue only happens when all of the replicated servers have no traffic? --Josh -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
