Re: CURRENT_DATE and CURRENT_TIME are broken

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: CURRENT_DATE and CURRENT_TIME are broken
Date: 2001-02-23 18:27:18
Message-ID: 200102231827.NAA17094@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> We have three choices:
>
> 1. Change these pg_proc entries. This does not force an initdb,
> exactly, but it won't take effect without one either.
>
> 2. Change the function calls emitted by the parser for
> CURRENT_DATE/TIME. This doesn't force an initdb either, but it's a
> workaround whereas #1 actually fixes the real bug. (Although #2 might
> appear to break stored rules in beta databases, any such rules are
> already broken because they've already been reduced to constants...)
>
> 3. Ship 7.1 with broken CURRENT_DATE/TIME functionality.
>
> I tend to favor #1, but need agreement to change it. Comments?
> If we do #1, should we bump catversion.h, or leave it alone?
> (I'd vote for not changing catversion, I think.)

I vote for anything but #2, and agree catversion should not be changed.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-02-23 18:28:14 Re: Lock structures
Previous Message The Hermit Hacker 2001-02-23 18:25:55 beta5 packages ...