Re: [GENERAL] CURRENT_TIMESTAMP

Josh Berkus wrote:
> 
> 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?

I thought the spec required it, but now that I see it doesn't, I don't
know why it was done that way.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073