Re: BUG #5118: start-status-insert-fatal

Поиск
Список
Период
Сортировка
От Kevin Grittner
Тема Re: BUG #5118: start-status-insert-fatal
Дата
Msg-id 4AD72DA1020000250002BA01@gw.wicourts.gov
обсуждение исходный текст
Ответ на Re: BUG #5118: start-status-insert-fatal  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: BUG #5118: start-status-insert-fatal  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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 по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #5118: start-status-insert-fatal
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #5118: start-status-insert-fatal