Re: CURRENT_TIMESTAMP

Michael Paesold wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> wrote:
> 
> > Yes, clearly, we will need to have all three time values available to
> > users.  With three people now suggesting we don't change, I will just
> > add to TODO:
> >
> > Add now("transaction|statement|clock") functionality
> >
> > Is that good?
> 
> CURRENT_TIMESTAMP etc. are converted to now()::TIMESTAMP, at least in 7.2,
> right?
> So when there are all three options available, it would be easy to change
> the behaviour of CURRENT_DATE/TIME/TIMESTAMP, right?
> 
> SET .. or GUC would be options, no?

Well, we are going to make all of them available in 7.4, but I don't see
a reason to have CURRENT_TIMESTAMP changing based on GUC.  If you want a
specific one, use now("string").

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