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

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Pedro Gimeno" <pgsql-003(at)personal(dot)formauri(dot)es>, <pgsql-bugs(at)postgresql(dot)org>, "Gerhard Leykam" <gel123(at)sealsystems(dot)de>
Subject: Re: BUG #5118: start-status-insert-fatal
Date: 2009-10-16 15:58:14
Message-ID: 4AD851C6020000250002BA9D@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Alternatively, do the postmaster support and make the
> presumably-minor pg_ctl mods to use it, and then a standalone
> pg_ping utility could come later. I'm not sure how big the utility
> would be, but surely bigger than the delta in pg_ctl.

Bigger than the delta for *just this change* to pg_ctl. I was
thinking of addressing all pg_ctl issues at once, but perhaps this
one makes sense on its own. If so, your alternative does sound
better.

-Kevin

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2009-10-16 16:19:01 Re: BUG #5121: Segmentation Fault when using pam w/ krb5
Previous Message Tom Lane 2009-10-16 15:48:05 Re: BUG #5118: start-status-insert-fatal