| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-patches(at)postgresql(dot)org, Brendan Jurd <direvus(at)gmail(dot)com> |
| Subject: | Re: Additional current timestamp values |
| Date: | 2006-03-20 23:02:06 |
| Message-ID: | 200603202302.k2KN26J07336@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > Rather than applying the above patch, I have implemented this TODO
> > with the attached patch:
> >
> > * Add transaction_timestamp(), statement_timestamp(),
> > clock_timestamp() functionality
>
> The most common complaint that I recall is that current_timestamp
> returns the transaction timestamp rather than the statement timestamp,
> which is what many expect. How does your patch address that?
No, we believe the standard requires it.
> Do we really need clock_timestamp?
Yes, because timeofday() returns a unix text string. Some people do
want a wallclock current timestamp.
--
Bruce Momjian http://candle.pha.pa.us
SRA OSS, Inc. http://www.sraoss.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2006-03-20 23:05:02 | Re: Additional current timestamp values |
| Previous Message | Peter Eisentraut | 2006-03-20 23:00:06 | Re: Additional current timestamp values |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-03-20 23:03:10 | Re: Removal of backward-compatibility docs mentions |
| Previous Message | Tom Lane | 2006-03-20 23:01:24 | Re: Removal of backward-compatibility docs mentions |