From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Configuring synchronous replication |
Date: | 2010-09-21 08:29:48 |
Message-ID: | AANLkTinGZd9+0ufRsSo2GmwTbp7cv=poOsgUKabBeoyd@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Sun, Sep 19, 2010 at 7:20 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sat, Sep 18, 2010 at 5:42 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>> There are considerable benefits to having a standby registry with a
>> table-like interface. Â Particularly, one where we could change
>> replication via UPDATE (or ALTER STANDBY) statements.
>
> I think that using a system catalog for this is going to be a
> non-starter, but we could use a flat file that is designed to be
> machine-editable (and thus avoid repeating the mistake we've made with
> postgresql.conf).
Yep, the standby registration information should be accessible and
changable while the server is not running. So using only system
catalog is not an answer.
My patch has implemented standbys.conf which was proposed before.
This format is the almost same as the pg_hba.conf. Is this
machine-editable, you think? If not, we should the format to
something like xml?
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-09-21 08:34:01 | Re: Configuring synchronous replication |
Previous Message | Dimitri Fontaine | 2010-09-21 08:24:35 | Re: Configuring synchronous replication |
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-09-21 08:34:01 | Re: Configuring synchronous replication |
Previous Message | Dimitri Fontaine | 2010-09-21 08:24:35 | Re: Configuring synchronous replication |