| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | 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:34:42 |
| Message-ID: | 15713.1092972882@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2004-08-20 03:36:32 | Re: tablespace and sequences? |
| Previous Message | Larry Rosenman | 2004-08-20 03:27:12 | Re: postgres uptime |