From: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
---|---|
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:07:35 |
Message-ID: | Pine.LNX.4.58.0408201306380.20472@linuxworld.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, 19 Aug 2004, Alvaro Herrera wrote:
> On Fri, Aug 20, 2004 at 09:43:13AM +0800, Christopher Kings-Lynne wrote:
> > >It seems that there is no way to know the postgres
> > >uptime, a sort of uptime() function could be usefull.
> > >I had recently the necessity of detect a node fail over,
> > >and the only way I can do it with a SQL connection is asking
> > >the engine uptime. Of course I can do it with PS but
> > >now that windows version is out I believe a platform
> > >indipendent way is required. Any objection to add it ?
> >
> > That sounds like a cool idea to me, although I would suggest a function
> > pg_uptime() that returns an interval or something.
> >
> > However, adding a new function requires a re-initdb, so it's quite
> > unlikely this will be in for 8.0.
>
> Is the uptime kept internally anywhere? Or even the start time?
We do this at the start of ServerLoop():
gettimeofday(&earlier, &tz);
and that value isn't changed, AFAICT. However, I'm not sure why an uptime
is all that useful?
Gavin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-20 03:09:11 | Re: tablespace and sequences? |
Previous Message | Bruce Momjian | 2004-08-20 03:05:52 | Re: postgres uptime |