| From: | Joshua Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Switching timeline over streaming replication |
| Date: | 2012-12-19 17:34:36 |
| Message-ID: | 1573826730.102138.1355938476056.JavaMail.root@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2012-12-19 17:39:58 | Re: Set visibility map bit after HOT prune |
| Previous Message | Pavan Deolasee | 2012-12-19 17:26:40 | Re: Set visibility map bit after HOT prune |