Re: [SQL] CURRENT_TIMESTAMP - Mailing list pgsql-general

From Tom Lane
Subject Re: [SQL] CURRENT_TIMESTAMP
Date
Msg-id 14617.1033358039@sss.pgh.pa.us
Whole thread Raw
In response to Re: [SQL] CURRENT_TIMESTAMP  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-general
Josh Berkus <josh@agliodbs.com> writes:
> Are we still planning on putting the three different versions of now() on the
> TODO?  I.e.,
> now('transaction'),
> now('statement'), and
> now('immediate')
> With now() = now('transaction')?

I have no objection to doing that.  What seems to be contentious is
whether we should change the current behavior of CURRENT_TIMESTAMP.

            regards, tom lane

pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Server to server communication
Next
From: Tom Lane
Date:
Subject: Re: [SQL] CURRENT_TIMESTAMP