From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, 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-11-26 19:19:51 |
Message-ID: | 201011261919.oAQJJp504942@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
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. +
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitriy Igrishin | 2010-11-26 20:26:19 | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |
Previous Message | Bala Murugan | 2010-11-26 18:06:53 | BUG #5773: DEBUG: reaping dead processes DEBUG: server process (PID 10007) was terminated by signal 11: Segme |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2010-11-26 19:54:24 | Re: duplicate connection failure messages |
Previous Message | Tom Lane | 2010-11-26 19:14:08 | Re: memory leak in libxml2 - fix |