From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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-11-17 20:03:04 |
Message-ID: | 201011172003.oAHK34T12699@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Agreed. So how do we pass that info to libpq without exceeding the
> > value of fixing this problem? Should we parse pg_controldata output?
> > pg_upgrade could use machine-readable output from that too.
>
> pg_controldata seems 100% unrelated to this problem. You cannot even
> tell if the postmaster is alive just by inspecting pg_control.
I was thinking of this:
$ pg_controldata /u/pg/data
...
Database cluster state: shut down
> >> What we actually want here, and don't have, is the fabled pg_ping
> >> protocol...
>
> > Well, we are basically figuring how to implement that with this fix,
> > whether it is part of pg_ctl or a separate binary.
>
> Possibly the cleanest fix is to implement pg_ping as a libpq function.
> You do have to distinguish connection failures (ie connection refused)
> from errors that came back from the postmaster, and the easiest place to
> be doing that is inside libpq.
OK, so a new libpq function --- got it. Would we just pass the status
from the backend or can it be done without backend modifications?
--
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 | Tom Lane | 2010-11-17 22:23:54 | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |
Previous Message | Tom Lane | 2010-11-17 19:55:33 | Re: Re: [BUGS] BUG #5650: Postgres service showing as stopped when in fact it is running |
From | Date | Subject | |
---|---|---|---|
Next Message | Dimitri Fontaine | 2010-11-17 20:05:09 | Re: ALTER TYPE recursion to typed tables |
Previous Message | Marc Cousin | 2010-11-17 20:00:50 | Re: Review: rollback sequence reset for TRUNCATE ... RESTART IDENTITY |