Re: pg_primary_conninfo
Guillaume Lelarge <guillaume@lelarge.info>
From: Guillaume Lelarge <guillaume@lelarge.info>
To: Gurjeet Singh <singh.gurjeet@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Magnus Hagander <magnus@hagander.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-12-28T17:02:01Z
Lists: pgsql-hackers
Le 28/12/2010 17:50, Gurjeet Singh a écrit : > 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. > The host should be the socket file path. -- Guillaume http://www.postgresql.fr http://dalibo.com