From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>, Mark Llewellyn <mark_llewellyn(at)adp(dot)com>, pgsql-hackers(at)postgresql(dot)org, Sujeet Rajguru <sujeet(dot)rajguru(at)enterprisedb(dot)com> |
Subject: | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |
Date: | 2010-09-24 14:42:48 |
Message-ID: | 4C9CB8E8.3040106@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On 09/24/2010 10:15 AM, Magnus Hagander wrote:
> On Fri, Sep 24, 2010 at 16:04, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Magnus Hagander<magnus(at)hagander(dot)net> writes:
>>> I took a quick look at the code, and from what I can tell this is
>>> because PQconnectionNeedsPassword() always returns false if a
>>> pgpass.conf has been used. There is no handling the case where pgpass
>>> is used, but has an incorrect password.
>> Why should it? That code is complicated enough, I don't think it needs
>> to have a behavior of pretending that a wrong entry isn't there.
> In that case, we should probably teach pg_ctl about this case, no?
> Since it clearly gives an incorrect message to the user now...
>
pg_ctl decides that the server is running iff it can connect to it. Do
you intend to provide for a different test? Setting an incorrect
password for the service account sounds like pilot error to me.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2010-09-24 14:52:43 | Re: installer problems |
Previous Message | Andreas Pflug | 2010-09-24 14:37:17 | Re: BUG #5675: out of memory at request size 32Mb |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-09-24 15:11:06 | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |
Previous Message | Heikki Linnakangas | 2010-09-24 14:15:53 | Re: Configuring synchronous replication |