From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | bricklen <bricklen(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Vik Fearing <vik(dot)fearing(at)dalibo(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_system_identifier() |
Date: | 2013-08-22 15:47:18 |
Message-ID: | 14073.1377186438@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
bricklen <bricklen(at)gmail(dot)com> writes:
> On Thu, Aug 22, 2013 at 6:42 AM, Andres Freund <andres(at)2ndquadrant(dot)com>wrote:
>> FWIW I've wished for that function repeatedly. Mostly just to make sure
>> I am actually connected to the same "network" of replicas and not some
>> other.
>> It's also useful if you're providing support for a limited number of
>> machines and you want some form of identifying a node.
> There's a "hostname" function at PGXN which serves some use-cases:
> http://pgxn.org/dist/hostname/
I have a very vague recollection that we might've intentionally decided
not to expose the system identifier at the SQL level. This could be all
wet, but it'd be worth trolling the archives to see if there was such a
conversation and if so whether the arguments still have merit.
See also recent discussion about changing how the identifier is computed
--- it'd be a good idea to fix that before we expose the identifier to
users, if we decide to do so.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick Dung | 2013-08-22 15:53:28 | several questions about pg_dumpall, pg_start_backup, pg_basebackup and WAL |
Previous Message | Josh Berkus | 2013-08-22 15:45:38 | Re: pg_system_identifier() |