Re: Synchronous replication

Поиск
Список
Период
Сортировка
От Greg Stark
Тема Re: Synchronous replication
Дата
Msg-id AANLkTineufXi05mZSq9t2LvxzdPns8sOHdGw7p1b9QCw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Synchronous replication  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Ответы Re: Synchronous replication  (Robert Haas <robertmhaas@gmail.com>)
Re: Synchronous replication  (Fujii Masao <masao.fujii@gmail.com>)
Re: Synchronous replication  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Список pgsql-hackers
On Sun, Aug 1, 2010 at 7:11 AM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Kevin Grittner"
Дата:
Сообщение: Re: review patch: Distinguish between unique indexes and unique constraints
Следующее
От: Robert Haas
Дата:
Сообщение: Re: review: psql: edit function, show function commands patch