Re: BUG #5118: start-status-insert-fatal - Mailing list pgsql-bugs

From Kevin Grittner
Subject Re: BUG #5118: start-status-insert-fatal
Date
Msg-id 4AD721C8020000250002B9EA@gw.wicourts.gov
Whole thread Raw
In response to Re: BUG #5118: start-status-insert-fatal  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #5118: start-status-insert-fatal
List pgsql-bugs
Tom Lane <tgl@sss.pgh.pa.us> wrote:

> I would rather see us implement the hypothetical pg_ping protocol
> and remember to include the postmaster's PID in the response.  One
> of the worst misfeatures of pg_ctl is the need to be able to
> authenticate itself to the postmaster, and having it rely on being
> able to actually issue a SQL command would set that breakage in
> stone.

Sounds good to me, other than it stalls pg_ctl revamp until pg_ping is
done.  I don't remember a clear design of what pg_ping should look
like.  Does anyone have a clear plan in their head?

-Kevin

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #5118: start-status-insert-fatal
Next
From: Tom Lane
Date:
Subject: Re: BUG #5120: Performance difference between running a query with named cursor and straight SELECT