Re: -d option for pg_isready is broken - Mailing list pgsql-hackers

From Tom Lane
Subject Re: -d option for pg_isready is broken
Date
Msg-id 1043.1386789009@sss.pgh.pa.us
Whole thread Raw
In response to Re: -d option for pg_isready is broken  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: -d option for pg_isready is broken
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Dec 11, 2013 at 11:24 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> In general, I think the definition of these query functions ought to
>> be "what was the value of this parameter when the connection was made".
>> As such, I'm not even sure that the pgunixsocket behavior that's in
>> PQhost now is a good idea, much less that we should extend that hack
>> to cover DefaultHost.

> Well, returning /tmp on Windows is just stupid.  I don't see why we
> should feel bad about changing that.  A bug is a bug.

What I was suggesting was we should take out the pgunixsocket fallback,
not make it even more complicated.  That probably implies that we need
still another accessor function to get the socket path.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Extension Templates S03E11
Next
From: Robert Haas
Date:
Subject: Re: preserving forensic information when we freeze