From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Wang Mike <itlist(at)msn(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: clock_timestamp() and transaction_timestamp() function |
Date: | 2003-11-30 17:42:31 |
Message-ID: | 200311301742.hAUHgVX12918@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > We have started 7.5 development so we can now work with you to complete
> > this item. Your question was what does statement_timestamp() show.
> > That has been discussed and it is a little tricky. The idea is that is
> > should be start of a single statement that arrives from the user or is
> > requestd by a client. However, this gets muddled because SPI can issue
> > queries and plpgsql functions can too.
>
> Are these supposed to be user-visible functions? What are they supposed
> to do?
Yes, user-visible. They give additional current timestamp information.
transaction_timestamp() is the same as current_timestamp,
clock_timestamp is the same as gettimeofday(), and statement_timestamp
is a new one that shows statement start time.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-11-30 17:44:48 | Re: Making pg_dump cvs friendly |
Previous Message | Peter Eisentraut | 2003-11-30 17:39:05 | Re: clock_timestamp() and transaction_timestamp() function |