Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running
Date
Msg-id AANLkTinqm4cY_e6C5cYh9Uf7gzX_-Vy475Z3ZO6_PKkr@mail.gmail.com
Whole thread Raw
Responses Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running
Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running
List pgsql-hackers
On Fri, Sep 17, 2010 at 05:51, Ashesh Vashi
<ashesh.vashi@enterprisedb.com> wrote:
> Hi Mark,
>
> On of my college (Sujeet) has found a way to reproduce the same behaviour.
> 1. Installed PG 9.0 on Win XP SP3
> 2. Stop the Postgresql-9.0 service from service manager console
> 3. Create pgpass.conf in postgres (service account) user's profile with an
> incorrect password deliberately.
> (Refer: http://www.postgresql.org/docs/8.4/interactive/libpq-pgpass.html)
> 4. Now start the postgresql-9.0 service, it will return an error and the
> status
>    shows stopped
> 5. However i could connect to the psql shell and get the prompt which means
>     the server is running.

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.

Does anybody recall the specific reason for this? Do we need a way for
pg_ctl to figure this out, or do we need to change it in
PQconnecitonNeedsPassword()?

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Dmitriy Igrishin
Date:
Subject: Large objects.
Next
From: Tom Lane
Date:
Subject: Re: pg_comments