Re: CONVERT function is seriously broken

From: "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CONVERT function is seriously broken
Date: 2002-11-02 10:59:17
Message-ID: 20021102065818.M42511-100000@hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 2 Nov 2002, Tom Lane wrote:

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Tom Lane wrote:
> >> Unfortunately, I don't see any way offhand to fix this without an
> >> initdb :-(.
>
> > Ooch, that hurts. How bad would it be if it was broken in 7.3?
>
> We could dike out the feature:
>
> convert_list:
> a_expr USING any_name
> {
> elog(ERROR, "CONVERT(... USING ...) is not implemented");
> }
>
> Short of that, I think we need an initdb to change the function
> signature for the convert() function. It needs to take a (suitably
> quoted) text parameter, not an OID.
>
> Since we forced initdb only a week ago with beta3, I don't think there
> is really a strong argument against doing it again. But probably Marc
> will say that we need a beta4 at this point, instead of going for RC1...

Most definitely ... but beta3 was nice and short, and no reason why beta4
can't be as well ...

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-11-02 14:26:56 Re: "Cache lookup failed for relation 16905" ??
Previous Message Philip Warner 2002-11-02 09:06:48 Re: Optimizer Question/Suggestion - numbers after