Re: pg_system_identifier()

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_system_identifier()
Date: 2013-08-22 16:25:00
Message-ID: 20130822162500.GH17006@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2013-08-22 12:18:41 -0400, Bruce Momjian wrote:
> On Thu, Aug 22, 2013 at 06:18:39PM +0200, Andres Freund wrote:
> > But essentially we already have something like that by the combination
> > of system identifier and timeline id. Admittedly there's the weakness
> > that the timelineid can increase the same on several machines in the
> > cluster but that's a weakness we ought to fix sometime independent of
> > this.
> >
> > So maybe the answer is to also expose the current timeline?
> >
> > An alternative would be to have a pg_controldata_values() SRF...
>
> It seems the value is more of a _cluster_ identifier than a system
> identifier. We don't allow cross-major-version replication, so I am
> confused why we can't rename it in 9.4.

For one, it would introduce confusion for the not inconsiderable number
of people already knowing the variable. For another, it's exposed via
the replication protocol's IDENTIFY SYSTEM.

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2013-08-22 16:30:59 Re: pg_system_identifier()
Previous Message Alvaro Herrera 2013-08-22 16:20:19 Re: pg_system_identifier()