Re: CURRENT_DATE and CURRENT_TIME are broken - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: CURRENT_DATE and CURRENT_TIME are broken
Date
Msg-id 200102231827.NAA17094@candle.pha.pa.us
Whole thread Raw
In response to CURRENT_DATE and CURRENT_TIME are broken  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: The Hermit Hacker
Date:
Subject: beta5 packages ...
Next
From: Bruce Momjian
Date:
Subject: Re: Lock structures