Re: gettime() - a timeofday() alternative

From: mark(at)mark(dot)mielke(dot)cc
To: Brendan Jurd <direvus(at)gmail(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: gettime() - a timeofday() alternative
Date: 2005-08-13 21:35:38
Message-ID: 20050813213538.GA30952@mark.mielke.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Sun, Aug 14, 2005 at 05:51:16AM +1000, Brendan Jurd wrote:
> Regarding the statement_timestamp() ... if the entire query path is
> parser -> rewriter -> planner/optimiser -> executor, what point in
> that path would be considered the true start of the "statement"? I
> would assume that it's right at the beginning, when it is first handed
> to the parser, but that's a very naive assumption.

The latest time before any index or table has been accessed to derive
results?

For prepared statements, for example, the time the statement was prepared
doesn't seem useful to me.

Cheers,
mark

--
mark(at)mielke(dot)cc / markm(at)ncf(dot)ca / markm(at)nortel(dot)com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada

One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...

http://mark.mielke.cc/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-08-13 22:24:01 Re: gettime() - a timeofday() alternative
Previous Message Brendan Jurd 2005-08-13 19:51:16 Re: gettime() - a timeofday() alternative

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2005-08-13 22:22:06 Re: [PATCH] Proposed: Have SPI_connect fail if there is no current snapshot
Previous Message Martijn van Oosterhout 2005-08-13 19:57:05 [PATCH] Proposed: Have SPI_connect fail if there is no current snapshot