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 4AD72DA1020000250002BA01@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'm not sure whether we'd want to provide a function within libpq
> for this, or just code it in pg_ctl.

I'm inclined to think there would be value to a pg_ping utility to
support automated monitoring by unprivileged users on other boxes.
That both suggests libpq as the location, and one or two additional
pieces of information.  An indication of "in archive recovery" versus
production or shutdown, for example, might be useful.  I'm not sure
what else might make sense.

> Within libpq the natural thing would be to take a conninfo
> connection string, but I'm not sure that suits pg_ctl's purposes.

I'm a little lost on that.  Would it cause any problems for pg_ctl,
or just be more than it would need if it's only implemented there?

-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 #5118: start-status-insert-fatal