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

Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.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@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073