From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, 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 20:30:49 |
Message-ID: | 15854.1290803449@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Fujii Masao wrote:
>> 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.
It's wrong though. If you get back a "password rejected" error, or most
other types of errors, it still indicates that the server started.
We just went over this a few days ago.
> 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?
No; it's useless and unnecessary behavior.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-11-26 20:39:33 | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |
Previous 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 |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-11-26 20:39:33 | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |
Previous 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 |