Horton

Re: [GENERAL] CURRENT_TIMESTAMP

Josh Berkus <josh@agliodbs.com>

View thread View on postgr.es
From: Josh Berkus <josh@agliodbs.com>
To: Bruce Momjian <pgman@candle.pha.pa.us>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: 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-24T01:53:36Z
Lists: pgsql-hackers, pgsql-general, pgsql-sql 
Tom, Bruce,

> > A possible compromise is to dissociate now() and current_timestamp,
> > allowing the former to be start of transaction and the latter to be
> > start of client command.
> 
> 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.

May I point out that this will break compatibility for those used to the 
current behavior?


-- 
-Josh Berkus
 Aglio Database Solutions
 San Francisco