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 4AD84BC9020000250002BA8D@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 was envisioning just using PostmasterRandom() (after initializing
> the seed from time(NULL) as we do now).  I don't think we need a
> super-wide random number.

Fine with me.  Just that and CanAcceptConnections in the response?

It seems like pg_ping (client utility and related postmaster support)
should be a discrete patch.  Improvements to pg_ctl and init scripts
would come later, as separate patches?

-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