On Thu, Aug 22, 2013 at 9:53 PM, Vik Fearing <vik.fear...@dalibo.com> wrote: > On 08/22/2013 02:51 PM, Fujii Masao wrote: >> On Thu, Aug 22, 2013 at 6:43 AM, Vik Fearing <vik.fear...@dalibo.com> wrote: >>> 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. >> What's the use case? > > It's information about the server that's only accessible through > pg_controldata.
BTW, you can see the system identifier by executing IDENTIFY_SYSTEM command in replication connection as follows: 1. Change the server settings so that the server can accept the replication connection 2. Connect to the server in replication mode 3. Execute IDENTIFY_SYSTEM command in replication connection $ psql "replication=1" =# IDENTIFY_SYSTEM; systemid | timeline | xlogpos ---------------------+----------+----------- 5914930202950905854 | 1 | 0/183F720 (1 row) This is not good way for a user, though ;P > I don't know if that's justification enough, which is > why I didn't add it to the commitfest yet. You can add the patch to CF, and then hear the opinions from other people during CF. Regards, -- Fujii Masao -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers