| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_system_identifier() |
| Date: | 2013-08-22 15:56:33 |
| Message-ID: | 20130822155633.GF17006@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-08-22 08:45:38 -0700, Josh Berkus wrote:
> All,
>
> Vik's feature would be useful for detecting an accidental split in a
> replication cluster. That is, it would be another tool for detecting if
> you've made a mistake and created two masters. So +1 from me.
>
> It will also be useful for me for sharding. Right now, I'm doing a
> hackish version of Vik's function, so I'd be glad to have it in core.
>
> However, given that the value is the same for all servers in a
> replication set, are we sure we want to call it system_identifier? Is
> there a better name?
Given it's been named that and visible via pg_controldata for years I am
against introducing confusion by renaming it.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-08-22 16:04:08 | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
| Previous Message | Tom Lane | 2013-08-22 15:55:32 | Re: pg_system_identifier() |