| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Markus Wanner <markus(at)bluegap(dot)ch>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Issues with Quorum Commit |
| Date: | 2010-10-13 06:43:36 |
| Message-ID: | 4CB55518.9060107@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 13.10.2010 08:21, Fujii Masao wrote:
> On Sat, Oct 9, 2010 at 4:31 AM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> It shouldn't be too hard to fix. Walsender needs to be able to read WAL from
>> preceding timelines, like recovery does, and walreceiver needs to write the
>> incoming WAL to the right file.
>
> And walsender seems to need to transfer the current timeline history to
> the standby. Otherwise, the standby cannot recover the WAL file with new
> timeline. And the standby might need to create the timeline history file
> in order to recover the WAL file with new timeline even after it's restarted.
Yes, true, you need that too.
It might be good to divide this work into two phases, teaching archive
recovery to notice new timelines appearing in the archive first, and
doing the walsender/walreceiver changes after that.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-10-13 06:45:16 | Re: Slow count(*) again... |
| Previous Message | Robert Haas | 2010-10-13 06:29:00 | Re: leaky views, yet again |