Re: Changing behavior of BEGIN...sleep...do something...COMMIT

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(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-03-30 02:38:22
Message-ID: 1859.1048991902@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2003-03-30 06:34:58 CVS head doesn't compile
Previous Message Bruce Momjian 2003-03-30 02:22:09 Re: Changing behavior of BEGIN...sleep...do something...COMMIT