Re: [GENERAL] CURRENT_TIMESTAMP - Mailing list pgsql-sql

From Josh Berkus
Subject Re: [GENERAL] CURRENT_TIMESTAMP
Date
Msg-id 200209231349.27237.josh@agliodbs.com
Whole thread Raw
In response to Re: [GENERAL] CURRENT_TIMESTAMP  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: [GENERAL] CURRENT_TIMESTAMP  (Bruce Momjian <pgman@candle.pha.pa.us>)
List 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
informationtechnology     josh@agliodbs.com   and data management solutions     (415) 565-7293  for law firms, small
businesses     fax 621-2533   and non-profit organizations.     San Francisco 



pgsql-sql by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [GENERAL] CURRENT_TIMESTAMP
Next
From: Bruce Momjian
Date:
Subject: Re: [GENERAL] CURRENT_TIMESTAMP