| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(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-20 06:29:55 |
| Message-ID: | 4C96FF63.8050808@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 19/09/10 01:20, Robert Haas 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).
Yeah, that needs some careful design. We also need to record transient
information about each slave, like how far it has received WAL already.
Ideally that information would survive database restart too, but maybe
we can live without that.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-09-20 09:17:29 | Re: Configuring synchronous replication |
| Previous Message | Heikki Linnakangas | 2010-09-20 06:27:15 | Re: Configuring synchronous replication |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vaibhav Kaushal | 2010-09-20 06:48:23 | Postgres Licensing |
| Previous Message | Heikki Linnakangas | 2010-09-20 06:27:15 | Re: Configuring synchronous replication |