| 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-12-01 02:54:40 |
| Message-ID: | 200312010254.hB12se322145@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Peter Eisentraut wrote:
> Bruce Momjian writes:
>
> > 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.
>
> And what would be the point of that?
The goal was to give a unified API to the various time measurements:
[clock|statement|transaction]_timestamp
--
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-12-01 03:26:40 | Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: |
| Previous Message | Bruce Momjian | 2003-12-01 02:51:16 | Re: Making pg_dump cvs friendly |