| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | 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-09-24 15:11:06 |
| Message-ID: | 25617.1285341066@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 09/24/2010 10:15 AM, Magnus Hagander wrote:
>> 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?
Seems like getting a password challenge from the server is sufficient
evidence that the server is running, whether we are able to meet the
challenge or not. Perhaps we could just twiddle pg_ctl's "is it up"
test a bit to notice whether the connect failure was of this sort.
(Of course, a "pg_ping" utility would be a better answer, but nobody's
gotten around to that in more than ten years, so I'm not holding my
breath.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2010-09-24 15:11:07 | Re: installer problems |
| Previous Message | Dave Page | 2010-09-24 15:10:09 | Re: installer problems |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2010-09-24 15:22:17 | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |
| Previous Message | Andrew Dunstan | 2010-09-24 14:42:48 | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |