Re: pg_primary_conninfo - Mailing list pgsql-hackers

From Gurjeet Singh
Subject Re: pg_primary_conninfo
Date
Msg-id AANLkTimz7Y32SfkKKb-zWGytsuXPyv4NYyf0oEKTLFAK@mail.gmail.com
Whole thread Raw
In response to Re: pg_primary_conninfo  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_primary_conninfo
List pgsql-hackers
On Tue, Dec 28, 2010 at 11:36 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

I can see the point of, say, a primary_host_address() function returning
inet, which would be way better on both those dimensions than the
current proposal.  But I'm not sure what else would be needed.


+1, since it bypasses security risks associated with exposing username/password.

Ability to see port number will be a useful addition.

Another case to consider is what if slave is connected to a local server over unix-domain sockets? Returning NULL might make it ambiguous with the case where the instance has been promoted out of standby.

Regards,
--
gurjeet.singh
@ EnterpriseDB - The Enterprise Postgres Company
http://www.EnterpriseDB.com

singh.gurjeet@{ gmail | yahoo }.com
Twitter/Skype: singh_gurjeet

Mail sent from my BlackLaptop device

pgsql-hackers by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Re: pg_primary_conninfo
Next
From: Tom Lane
Date:
Subject: Re: pg_dump --split patch