Re: CURRENT_TIMESTAMP

Bruce Momjian <pgman@candle.pha.pa.us> wrote:

> Yes, clearly, we will need to have all three time values available to
> users.  With three people now suggesting we don't change, I will just
> add to TODO:
>
> Add now("transaction|statement|clock") functionality
>
> Is that good?

CURRENT_TIMESTAMP etc. are converted to now()::TIMESTAMP, at least in 7.2,
right?
So when there are all three options available, it would be easy to change
the behaviour of CURRENT_DATE/TIME/TIMESTAMP, right?

SET .. or GUC would be options, no?

Best Regards,
Michael Paesold