From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Joseph Shraibman <joseph(at)xtenit(dot)com>, nolan(at)celery(dot)tssi(dot)com, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: fomatting an interval |
Date: | 2003-05-13 04:29:22 |
Message-ID: | 20030513042922.GI5081@dcc.uchile.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, May 12, 2003 at 11:49:23PM -0400, Tom Lane wrote:
> Joseph Shraibman <joseph(at)xtenit(dot)com> writes:
> 2003-01-08 19:58 tgl
>
> * src/include/catalog/pg_proc.h: Add missing pg_proc entry for
> interval_scale(). The lack of this entry causes interval rounding
> not to work as expected in 7.3, for example SELECT
> '18:17:15.6'::interval(0) does not round the value. I did not
> force initdb, but one is needed to install the added row.
>
> We could backpatch this into the 7.3 branch, but it would only help
> people who recompiled *and* re-initdb'd from the 7.3.3 sources. I
> thought at the time it'd just create confusion to do that. I'm willing
> to listen to other opinions though ...
Given that recompiling and adding the new tuple into pg_proc by means of
a simple INSERT(*) should be enough, it's hardly necessary to force an
initdb. Much less if there are not too many complaints, and a forced
initdb would force a dump/restore cycle that no one would like.
(*) It _can_ be done, right?
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Everybody understands Mickey Mouse. Few understand Hermann Hesse.
Hardly anybody understands Einstein. And nobody understands Emperor Norton."
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-05-13 04:55:48 | Re: fomatting an interval |
Previous Message | Tom Lane | 2003-05-13 03:49:23 | Re: fomatting an interval |