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  (Guillaume Lelarge <guillaume@lelarge.info>)
List pgsql-hackers
<div dir="ltr"><div class="gmail_quote">On Tue, Dec 28, 2010 at 11:36 AM, Tom Lane <span dir="ltr"><<a
href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>></span>wrote:<br /><blockquote class="gmail_quote"
style="margin:0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><br /> I can see the
pointof, say, a primary_host_address() function returning<br /> inet, which would be way better on both those
dimensionsthan the<br /> current proposal.  But I'm not sure what else would be needed.<br /><br
/></blockquote></div><br/>+1, since it bypasses security risks associated with exposing username/password.<br /><br
/>Abilityto see port number will be a useful addition.<br clear="all" /><br />Another case to consider is what if slave
isconnected to a local server over unix-domain sockets? Returning NULL might make it ambiguous with the case where the
instancehas been promoted out of standby.<br /><br />Regards,<br />-- <br />gurjeet.singh<br />@ EnterpriseDB - The
EnterprisePostgres Company<br /><a href="http://www.EnterpriseDB.com">http://www.EnterpriseDB.com</a><br /><br
/>singh.gurjeet@{gmail | yahoo }.com<br />Twitter/Skype: singh_gurjeet<br /><br />Mail sent from my BlackLaptop
device<br/></div> 

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