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>
Cc: Manfred Koizar <mkoi-pg@aon.at>, Tom Lane <tgl@sss.pgh.pa.us>, Aaron Held <aaron@MetroNY.com>, Roberto Mello <rmello@cc.usu.edu>, Neil Conway <neilc@samurai.com>, pgsql-sql@postgresql.org
Date: 2002-09-23T20:49:27Z
Lists: pgsql-hackers, pgsql-general, pgsql-sql 
Bruce,

> I don't see how we can defend returning the start of the transaction as
> the current_timestamp.  In a multi-statement transaction, that doesn't
> seem very current to me.  I know there are some advantages to returning
> the same value for all queries in a transaction, but is that value worth
> returning such stale time information?

Then what *was* the reasoning behind the current behavior?

-- 
-Josh Berkus

______AGLIO DATABASE SOLUTIONS___________________________
                                        Josh Berkus
   Complete information technology 	josh@agliodbs.com
    and data management solutions 	(415) 565-7293
   for law firms, small businesses 	 fax 621-2533
    and non-profit organizations. 	San Francisco