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

From Tom Lane
Subject Re: BUG #5118: start-status-insert-fatal
Date
Msg-id 12033.1255633179@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #5118: start-status-insert-fatal  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-bugs
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> [ thinks... ]  Maybe we could have the postmaster generate a random
>> number at start and include that in both the postmaster.ports file
>> and its pg_ping responses.

> Unless two postmasters could open the same server socket within a
> microsecond of one another, a timestamp value captured on opening the
> server socket seems even better than a random number.

Well, that raises the question of whether postmaster uptime could be
considered security-sensitive info.  I'd still rather use a random
number.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Postgresql 8.4.1 segfault, backtrace
Next
From: "Kevin Grittner"
Date:
Subject: Re: BUG #5118: start-status-insert-fatal