pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Hannu Krosing <hannu@2ndQuadrant.com>
To: Jim Nasby <jim@nasby.net>
Cc: Greg Stark <stark@mit.edu>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@2ndquadrant.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: pg_system_identifier()
Date: Mon, 26 Aug 2013 10:30:41 +0200
Message-ID: <521B1231.3080709@2ndQuadrant.com> (raw)
In-Reply-To: <521A8985.2040509@nasby.net>
References: <5215346B.7070800@dalibo.com>
	<CAHGQGwHN0114tzFnV2e3Pk8L74vHmDjPk7g73woK9B7xirT5pw@mail.gmail.com>
	<20130822134205.GC17006@awork2.anarazel.de>
	<WM!f248d514cddac81a49ad91107b7891d203688a9bc9b2b185a57c1442043f35ed99f6fc76707f6f71a7a8c9d2e425e9ba!@asav-3.01.com>
	<52163222.9030700@agliodbs.com>
	<20130822155633.GF17006@awork2.anarazel.de>
	<14611.1377187563@sss.pgh.pa.us>
	<20130822161839.GG17006@awork2.anarazel.de>
	<20130822162019.GC10710@eldon.alvh.no-ip.org>
	<20130822163059.GI17006@awork2.anarazel.de>
	<15653.1377189456@sss.pgh.pa.us>
	<52177AD5.5010809@2ndQuadrant.com>
	<CAM-w4HMJc+7OCDUFYD=ChWSp6jxBRPContr3Y2Y3py5swwaxig@mail.gmail.com>
	<521A8985.2040509@nasby.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On 08/26/2013 12:47 AM, Jim Nasby wrote:
> On 8/23/13 11:23 AM, Greg Stark wrote:
>> This doesn't generate a unique id. You could back up a standby and
>> restore it and point it at the original master and end up with two
>> standbies with the same id.
Yeah, not as easy as I imagined. It will fix itself once the 2nd slave
starts to follow the 1st, bt this has the disadvantage that for a
connected client a running system suddenly changes its "unique id".

If we want it happen automatically we have to allow erring on "too
often" or "not often enough" side for some users/usages.
>
> If you want to enforce something unique throughout a cluster, I think
> we're stuck with having the cluster communicate IDs across an entire
> cluster. AFAIK that's how both Slony and londiste 3 do it.
>
> I think it's also noteworthy that Slony and londiste both rely on the
> user specifying node identifiers. They don't try to be magic about it.
> I think there's 2 advantages there:
>
> - Code is simpler
> - Users can choose a naming schema that makes sense for them
3rd - really only users can determine when a "system" is unique and when
it is a copy of another.


Cheers

-- 
Hannu Krosing
PostgreSQL Consultant
Performance, Scalability and High Availability
2ndQuadrant Nordic OÜ



-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (43+ messages)  latest in thread

Message-ID: <521B1231.3080709@2ndQuadrant.com>
Permalink:  ../521B1231.3080709@2ndQuadrant.com/
Also on:    postgresql.org/message-id/521B1231.3080709@2ndQuadrant.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: hannu@2ndQuadrant.com, jim@nasby.net, stark@mit.edu, tgl@sss.pgh.pa.us, andres@2ndquadrant.com, alvherre@2ndquadrant.com, josh@agliodbs.com
  Subject: Re: pg_system_identifier()
  In-Reply-To: <521B1231.3080709@2ndQuadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox