From: | Gaetano Mendola <mendola(at)bigfoot(dot)com> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Subject: | Re: postgres uptime |
Date: | 2004-08-20 09:34:53 |
Message-ID: | 4125C5BD.9060302@bigfoot.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Richard Huxton wrote:
> Tom Lane wrote:
>
>> "Marc G. Fournier" <scrappy(at)postgresql(dot)org> writes:
>>
>>> Does anyone have any 'benefits' to implementing such a thing that we
>>> can list? The cons appear to be easy, what about pros?
>>
>>
>>
>> That's exactly what's bugging me --- I have not seen any particularly
>> strong defense of why we *should* have this function.
>>
>> Your suggestion in another mail of restricting it to superusers would
>> eliminate most or all of the security gripes I'm raising. Whether that
>> still leaves it useful to the original suggestor's purpose, I dunno...
>
>
> If you had a pressing need, couldn't you just hack the startup script(s)
> to insert a timestamp in a suitable table?
>
> Or am I missing something here (as usual)?
That's right, I'm not stuck with this problem I solved it with `ps`, I suggested
a global uptime function considering that postgres is not snmp capable and
for windows administrators is a bit more difficult retrieve this value.
Regards
Gaetano Mendola
From | Date | Subject | |
---|---|---|---|
Next Message | Gaetano Mendola | 2004-08-20 09:41:00 | Re: postgres uptime |
Previous Message | Gaetano Mendola | 2004-08-20 09:11:35 | Re: postgres uptime |