| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Vik Fearing <vik(dot)fearing(at)dalibo(dot)com> |
| Cc: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_system_identifier() |
| Date: | 2013-08-23 07:10:15 |
| Message-ID: | alpine.DEB.2.02.1308230838480.3533@localhost6.localdomain6 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> After someone in IRC asked if there was an equivalent to MySQL's
> server_id, it was noted that we do have a system identifier but it's not
> very accessible.
>
> The attached patch implements a pg_system_identifier() function that
> exposes it.
Would it make sense for such identifiers be standard UUID
(http://en.wikipedia.org/wiki/UUID)?
Should there be a UUID per cluster? and/or per database, possibly deduce
from the cluster one? Should it be configurable, say from
"postgresql.conf"?
get_pg_uuid()
get_pg_uuid('template0')
Note that there is a set of uuid functions provided as a module that may
help.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sawada Masahiko | 2013-08-23 07:42:23 | Behaviour of take over the synchronous replication |
| Previous Message | Pavel Stehule | 2013-08-23 06:38:32 | Re: PL/pgSQL, RAISE and error context |