Horton

Re: [GENERAL] CURRENT_TIMESTAMP

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

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: josh@agliodbs.com, Manfred Koizar <mkoi-pg@aon.at>, Aaron Held <aaron@MetroNY.com>, Roberto Mello <rmello@cc.usu.edu>, Neil Conway <neilc@samurai.com>, pgsql-sql@postgresql.org
Date: 2002-09-24T03:35:13Z
Lists: pgsql-hackers, pgsql-general, pgsql-sql 
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> I was thinking 'transaction_timestamp' for the transaction start time, and
> current_timestamp for the statement start time.  I would equate now()
> with current_timestamp.

So you want to both (a) invent even more nonstandard syntax than we
already have, and (b) break as many traditional-Postgres applications
as you possibly can?

'transaction_timestamp' has no reason to live.  It's not in the spec.
And AFAIK the behavior of now() has been well-defined since the
beginning of Postgres.  If you want to change 'current_timestamp' to
conform to a rather debatable reading of the spec, then fine --- but
keep your hands off of now().

			regards, tom lane