| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-patches(at)postgresql(dot)org |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Brendan Jurd <direvus(at)gmail(dot)com> |
| Subject: | Re: Additional current timestamp values |
| Date: | 2006-03-20 23:00:06 |
| Message-ID: | 200603210000.07477.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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?
Do we really need clock_timestamp?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-03-20 23:02:06 | Re: Additional current timestamp values |
| Previous Message | Bruce Momjian | 2006-03-20 22:34:24 | Additional current timestamp values |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-03-20 23:01:24 | Re: Removal of backward-compatibility docs mentions |
| Previous Message | Bruce Momjian | 2006-03-20 22:34:24 | Additional current timestamp values |