Re: pg_system_identifier() - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: pg_system_identifier()
Date
Msg-id 52163222.9030700@agliodbs.com
Whole thread Raw
In response to pg_system_identifier()  (Vik Fearing <vik.fearing@dalibo.com>)
Responses Re: pg_system_identifier()  (Andres Freund <andres@2ndquadrant.com>)
Re: pg_system_identifier()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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?

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com



pgsql-hackers by date:

Previous
From: Blake Smith
Date:
Subject: Hstore: Query speedups with Gin index
Next
From: Tom Lane
Date:
Subject: Re: pg_system_identifier()