Horton

Re: [SQL] CURRENT_TIMESTAMP

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: Martijn van Oosterhout <kleptog@svana.org>, Bruce Momjian <pgman@candle.pha.pa.us>, Manfred Koizar <mkoi-pg@aon.at>, Roland Roberts <roland@astrofoto.org>, pgsql-sql@postgresql.org, pgsql-general@postgresql.org
Date: 2002-09-30T03:53:59Z
Lists: pgsql-hackers, pgsql-general, pgsql-sql 
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