| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Petr Jelinek <petr(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Set new system identifier using pg_resetxlog |
| Date: | 2014-06-18 17:44:56 |
| Message-ID: | 53A1D018.9010608@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 06/13/2014 05:31 PM, Petr Jelinek wrote:
> Hello,
>
> attached is a simple patch which makes it possible to change the system
> identifier of the cluster in pg_control. This is useful for
> individualization of the instance that is started on top of data
> directory produced by pg_basebackup - something that's helpful for
> logical replication setup where you need to easily identify each node
> (it's used by Bidirectional Replication for example).
I'm unclear on why we would overload pg_resetxlog for this. Wouldn't it
be better design to have an independant function,
"pg_set_system_identifier"?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-06-18 17:46:26 | Re: Set new system identifier using pg_resetxlog |
| Previous Message | Andres Freund | 2014-06-18 17:40:09 | Re: Set new system identifier using pg_resetxlog |