Re: CURRENT_TIMESTAMP

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Michael Paesold <mpaesold(at)gmx(dot)at>
Cc: Thomas Lockhart <lockhart(at)fourpalms(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Sullivan <andrew(at)libertyrms(dot)info>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CURRENT_TIMESTAMP
Date: 2002-10-04 17:48:44
Message-ID: 200210041748.g94HmiM27076@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Paesold wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-10-04 17:53:19 Re: any experience with IA-64
Previous Message Bruce Momjian 2002-10-04 17:45:58 Re: numeric hierarchy again (was Re: floor function in 7.3b2)