| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Doug McNaught <doug(at)mcnaught(dot)org>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Changing behavior of BEGIN...sleep...do something...COMMIT |
| Date: | 2003-05-26 18:35:54 |
| Message-ID: | 200305261835.h4QIZsO10723@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Doug McNaught wrote:
> >> Maybe clock_time() and statement_time(), with transaction_time() an
> >> alias for now() (if that's seemed necessary)?
>
> I could go with that ...
>
> > We already have CURRENT_TIMESTAMP. Would CLOCK_TIMESTAMP,
> > TRANSACTION_TIMESTAMP, and STATEMENT_TIMESTAMP make sense, with
> > CURRENT_TIMESTAMP being the same as TRANSACTION_TIMESTAMP?
>
> ... or that. But, please, *not* the weird no-parentheses syntax that
> CURRENT_TIMESTAMP has. Make it clock_timestamp() and so on.
TODO updated:
* Add transaction_timestamp(), statement_timestamp(), clock_timestamp()
functionality
--
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-05-26 18:36:34 | Re: Changing behavior of BEGIN...sleep...do something...COMMIT |
| Previous Message | Bruce Momjian | 2003-05-26 18:32:33 | Re: [HACKERS] ECPG thread-safety |