Re: postgres uptime

From: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
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:56:51
Message-ID: 20040820005609.D28550@ganymede.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 19 Aug 2004, 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.

Couldn't it be stored in shared memory?

> 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.

Wouldn't an attacker have to have access to the server in the first place
to get that information?

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2004-08-20 04:04:29 Re: postgres uptime
Previous Message Tom Lane 2004-08-20 03:47:17 Re: tablespace and sequences?