From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Markus Schiltknecht <markus(at)bluegap(dot)ch> |
Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Shane Ambler <pgsql(at)007Marketing(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Integrating Replication into Core |
Date: | 2006-11-22 18:48:35 |
Message-ID: | 20061122184835.GI6804@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers |
Markus Schiltknecht wrote:
> >However, there may not be nifty syntax changes nor GUCs in core to
> >support a specific implementation of a replicator.
>
> I'd love to get into that one. Some of the people who have attended my
> talk at the summit might know that I've introduced the following syntax
> to Postgres-R:
>
> ALTER DATABASE testdb START REPLICATION IN GROUP testgroup USING egcs;
>
> And I'm using the system catalogs to store replication settings. What's
> so wrong with that?
I don't know if there's anything wrong, but in Mammoth Replicator, the
syntax to enable replication of a single table is
ALTER TABLE foo ENABLE REPLICATION
and we store the replication settings in system catalogs as well.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Schiltknecht | 2006-11-22 18:56:03 | Re: Integrating Replication into Core |
Previous Message | Markus Schiltknecht | 2006-11-22 18:23:30 | Integrating Replication into Core |
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Schiltknecht | 2006-11-22 18:56:03 | Re: Integrating Replication into Core |
Previous Message | Andrew Dunstan | 2006-11-22 18:37:57 | Re: FKs + partial indexes? |