From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | Yeb Havinga <yebhavinga(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Sync Rep v19 |
Date: | 2011-03-05 16:17:29 |
Message-ID: | AANLkTimCtke=G0YKakCDJoNMCnX6gc0LwB1_QrdXgT+x@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Mar 6, 2011 at 12:07 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> I'm not in favour.
>
> If the user has a preferred order, they can specify it. If there is no
> preferred order, how will we maintain that order?
>
> What are the rules for maintaining this arbitrary order?
Probably what Robert, Yeb and I think is to leave the current
sync standby in sync mode until either its connection is closed
or higher priority standby connects. No complicated rule is
required.
To do that, how about tracking which standby is currently in
sync mode? Each walsender checks whether its priority is
higher than that of current sync one, and if yes, it takes over.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2011-03-05 16:23:03 | Re: Alpha4 release blockers (was Re: wrapping up this CommitFest) |
Previous Message | Fujii Masao | 2011-03-05 15:42:20 | Re: Sync Rep v19 |