Re: select_common_collation callers way too ready to throw error - Mailing list pgsql-hackers

From Tom Lane
Subject Re: select_common_collation callers way too ready to throw error
Date
Msg-id 21527.1299788091@sss.pgh.pa.us
Whole thread Raw
In response to Re: select_common_collation callers way too ready to throw error  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> On ons, 2011-03-09 at 18:07 -0500, Tom Lane wrote:
>> Now the downside of that is that a runtime failure won't give you an
>> parse error pointer to indicate which function is having trouble ...
>> but having an error pointer for an error that shouldn't be thrown in
>> the first place is small consolation.

> Sounds reasonable.

> Btw., the ultimate plan here was that functions or operators that would
> care about collation would be marked as such in pg_proc.  That plan
> basically just ran out of time, but if you think it'd be useful, maybe
> we could reactivate it quickly.

I think it's worth doing at some point, but not right now.  By the time
you get done adding support for the flag to CREATE FUNCTION, pg_dump,
etc, it's not a small task.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: configure gaps
Next
From: Peter Eisentraut
Date:
Subject: Re: Theory of operation of collation patch