Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running

Hey hackers,

I am sorry, but is it possible to implement BTW ability to
check exactly status of authentication from libpq ? As for now,
the only way to check failed authentication is parsing the error
message, that is sadly.

2010/11/26 Bruce Momjian <bruce(at)momjian(dot)us>

> Fujii Masao wrote:
> > On Fri, Nov 26, 2010 at 3:11 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > > I have applied this patch, with modified wording of the "cannot
> connect"
> > > case:
> > >
> > > ? ? ? ?$ pg_ctl -w -l /dev/null start
> > > ? ? ? ?waiting for server to start.... done
> > > ? ? ? ?server started
> > > ? ? ? ?warning: ?could not connect, perhaps due to invalid
> authentication or
> > > ? ? ? ?misconfiguration.
> >
> > This patch breaks the behavior that "pg_ctl -w start" waits until the
> standby
> > has been ready to accept read-only queries. IOW, pg_ctl without this
> patch
> > continues to check the connection even if the connection is rejected
> because
> > the database has not been consistent yet. But pg_ctl with this patch
> treats
> > that rejection as success of the standby starting and prints the above
> > messages.
> >
> > I agree to treat the receipt of password request from the server as
> success
> > of the server starting. But I don't think that we should treat other
> rejection
> > cases that way and change the existing behavior.
>
> OK, that is easy to fix. The only downside is that if you misconfigured
> .pgpass (which is what I used for testing), you have to wait 60 seconds
> to get the "cannot connect" error message. Is that OK?
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + It's impossible for everything to be true. +
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

--
// Dmitriy.