Re: Changing behavior of BEGIN...sleep...do something...COMMIT - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Changing behavior of BEGIN...sleep...do something...COMMIT
Date
Msg-id 1859.1048991902@sss.pgh.pa.us
Whole thread Raw
In response to Re: Changing behavior of BEGIN...sleep...do something...COMMIT  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Changing behavior of BEGIN...sleep...do something...COMMIT  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
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.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Changing behavior of BEGIN...sleep...do something...COMMIT
Next
From: Alvaro Herrera
Date:
Subject: CVS head doesn't compile