Re: Do we really want to migrate plproxy and citext into PG core distribution? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Do we really want to migrate plproxy and citext into PG core distribution?
Date
Msg-id 27082.1217274561@sss.pgh.pa.us
Whole thread Raw
In response to Re: Do we really want to migrate plproxy and citext into PG core distribution?  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Do we really want to migrate plproxy and citext into PG core distribution?  (Andrew Dunstan <andrew@dunslane.net>)
Re: Do we really want to migrate plproxy and citext into PG core distribution?  (Martijn van Oosterhout <kleptog@svana.org>)
Re: Do we really want to migrate plproxy and citext into PG core distribution?  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Tom Lane wrote:
>> Well, it won't make it harder to implement collations; but I worry that
>> people who have been relying on the citext syntax will have a hard time
>> migrating to collations.  Perhaps if someone did the legwork to
>> determine exactly what that conversion would look like, it would assuage
>> the fear.

> I kind of assumed we would do it by implementing the COLLATE clause of 
> the CREATE DOMAIN statement.

But to define such a domain, you'd have to commit to a case-insensitive
version of a specific collation, no?  citext currently means "case
insensitive version of whatever the database's default collation is".
This might be worrying over nothing significant, but I'm not
convinced...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Do we really want to migrate plproxy and citext into PG core distribution?
Next
From: Andrew Gierth
Date:
Subject: Re: WITH RECUSIVE patches 0723