From: | Lee Kindness <lkindness(at)csl(dot)co(dot)uk> |
---|---|
To: | "Tim Knowles" <tim(at)ametco(dot)co(dot)uk> |
Cc: | Lee Kindness <lkindness(at)csl(dot)co(dot)uk>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postmaster Uptime |
Date: | 2002-09-25 09:36:12 |
Message-ID: | 15761.33676.639067.205109@kelvin.csl.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tim, given this is purely cosmetic I'm sure you'd be hardpushed
getting it added to PostgreSQL proper.
As others have said it is certainly do-able, but you're going to have
to do it! In the past you've got the uptime using ps - what you need
to do is wrap this into a script and add it to a database as a
function (using pg/tcl, pg/perlu, whatever). Or you could do it as a C
function...
Lee.
Tim Knowles writes:
> To be honest my reason for requiring an uptime is really just comestic. My
> company uses a VBA app with PostgreSQL as the backend, an administrator only
> screen shows database activity (number of backends, running queries -
> bascially custom versions of some of the pg_stat views), I thought the
> uptime would be an interesting addition to that.
>
> I also think that having easy access to the uptime could help in the
> advocacy of PostgreSQL. My best is just over 4 months (based on the date
> given by the ps command), stopped only by an upgrade to 7.2.2! If people are
> willing to publish/share that sort of info it can only further impress
> people about PostgreSQL's stability (btw I've never had a crash/problem in
> the 2 years I've been using PostgreSQL)
From | Date | Subject | |
---|---|---|---|
Next Message | Lee Kindness | 2002-09-25 09:39:02 | Re: Postmaster Uptime |
Previous Message | Thomas O'Dowd | 2002-09-25 09:23:32 | Re: Postmaster Uptime |