Peter Eisentraut wrote:
> On fre, 2010-12-31 at 17:26 -0500, Bruce Momjian wrote:
> > Patch applied, and TODO item removed because patch mostly detects if a
> > stale postmaster created the postmaster.pid file. The TODO was:
>
> Please fix this new compiler warning:
>
> pg_ctl.c:1787: warning: i
On fre, 2010-12-31 at 17:26 -0500, Bruce Momjian wrote:
> Patch applied, and TODO item removed because patch mostly detects if a
> stale postmaster created the postmaster.pid file. The TODO was:
Please fix this new compiler warning:
pg_ctl.c:1787: warning: implicit declaration of function ‘time’
Bruce Momjian wrote:
> Bruce Momjian wrote:
> > Yes, that was my calculus too. I realized that we create session ids by
> > merging the process id and backend start time, so I went ahead and added
> > the postmaster start time epoch to the postmaster.pid file. While there
> > is no way to pass ba
Bruce Momjian wrote:
> Yes, that was my calculus too. I realized that we create session ids by
> merging the process id and backend start time, so I went ahead and added
> the postmaster start time epoch to the postmaster.pid file. While there
> is no way to pass back the postmaster start time fr
Tom Lane wrote:
> Bruce Momjian writes:
> > While I am working on pg_ctl, I saw this TODO item:
> > Have the postmaster write a random number to a file on startup that
> > pg_ctl checks against the contents of a pg_ping response on its initial
> > connection (without login)
>
>
Bruce Momjian writes:
> While I am working on pg_ctl, I saw this TODO item:
> Have the postmaster write a random number to a file on startup that
> pg_ctl checks against the contents of a pg_ping response on its initial
> connection (without login)
> This will
While I am working on pg_ctl, I saw this TODO item:
Have the postmaster write a random number to a file on startup that
pg_ctl checks against the contents of a pg_ping response on its initial
connection (without login)
This will protect against connecti
