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

From Bruce Momjian
Subject Re: [GENERAL] CURRENT_TIMESTAMP
Date
Msg-id 200209240201.g8O216G22740@candle.pha.pa.us
Whole thread Raw
In response to Re: [GENERAL] CURRENT_TIMESTAMP  (Josh Berkus <josh@agliodbs.com>)
Responses Re: [GENERAL] CURRENT_TIMESTAMP  (John Hasler <john@dhh.gt.org>)
List pgsql-sql
Josh Berkus wrote:
> 
> 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?

I am not saying we have to make that change.  My point is that our
current behavior may not be the most intuitive, and that most people may
prefer a change.  Any such change would be documented in the release
notes.

--  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
 


pgsql-sql by date:

Previous
From: Josh Berkus
Date:
Subject: Re: [GENERAL] CURRENT_TIMESTAMP
Next
From: Josh Berkus
Date:
Subject: Re: Performance w/ multiple WHERE clauses