| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | hlinnaka(at)iki(dot)fi |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Cascading replication and recovery_target_timeline='latest' |
| Date: | 2012-09-04 00:40:22 |
| Message-ID: | 50454DF6.4070400@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03.09.2012 16:26, Heikki Linnakangas wrote:
> On 03.09.2012 16:25, Fujii Masao wrote:
>> On Tue, Sep 4, 2012 at 7:07 AM, Heikki Linnakangas<hlinnaka(at)iki(dot)fi>
>> wrote:
>>> Hmm, I was thinking that when walsender gets the position it can send
>>> the
>>> WAL up to, in GetStandbyFlushRecPtr(), it could atomically check the
>>> current
>>> recovery timeline. If it has changed, refuse to send the new WAL and
>>> terminate. That would be a fairly small change, it would just close the
>>> window between requesting walsenders to terminate and them actually
>>> terminating.
>>
>> Yeah, sounds good. Could you implement the patch? If you don't have time,
>> I will....
>
> I'll give it a shot..
So, this is what I came up with, please review.
- Heikki
| Attachment | Content-Type | Size |
|---|---|---|
| disconnect-walsenders-on-target-tli-change.patch | text/x-diff | 8.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2012-09-04 00:58:21 | Re: Reduce the time to know trigger_file's existence |
| Previous Message | Heikki Linnakangas | 2012-09-03 23:26:33 | Re: Cascading replication and recovery_target_timeline='latest' |