| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Joshua Tolley <eggyknap(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Yeb Havinga <yebhavinga(at)gmail(dot)com>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Synchronous replication |
| Date: | 2010-08-01 12:30:08 |
| Message-ID: | AANLkTineufXi05mZSq9t2LvxzdPns8sOHdGw7p1b9QCw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Aug 1, 2010 at 7:11 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> In fact, it's possible for one standby to sync up to X, then disconnect and
> reconnect, and have the master count it second time in the quorum.
> Especially if the master doesn't notice that the standby disconnected, e.g a
> network problem.
>
> I don't think any of this quorum stuff makes much sense without explicitly
> registering standbys in the master.
This doesn't have to be done manually. The streaming protocol could
include the standby sending its system id to the master. The master
could just keep a list of system ids with the last record they've been
sent and the last they've confirmed receipt, fsync, application,
whatever the protocol covers. If the same system reconnects it just
overwrites the existing data for that system id.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-08-01 12:37:23 | Re: review: psql: edit function, show function commands patch |
| Previous Message | Kevin Grittner | 2010-08-01 10:54:09 | Re: review patch: Distinguish between unique indexes and unique constraints |