From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Gaetano Mendola <mendola(at)bigfoot(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: postgres uptime |
Date: | 2004-08-20 03:47:11 |
Message-ID: | 200408200347.i7K3lBx15964@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> writes:
> > Is the uptime kept internally anywhere? Or even the start time?
>
> No, and no (at least not in any globally accessible variable).
>
> > If it is, it would be quite trivial to provide access to it
>
> Not really --- in the EXEC_BACKEND case, we'd have to do something
> explicit to pass the value down to backends.
>
> I'd like to see more than one person requesting this (and with solider
> rationales) before it gets added to TODO. If I wanted to be picky I
> would suggest that knowledge of the server start time might be useful
> information to an attacker. It would for instance narrow down the
> number of possible starting seeds for the postmaster's random number
> generator.
I have already seen several people who are interested in it for adding
it to TODO.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-20 03:47:17 | Re: tablespace and sequences? |
Previous Message | Bruce Momjian | 2004-08-20 03:46:09 | Re: tablespace and sequences? |