Re: Do we really want to migrate plproxy and citext into PG core distribution?

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Do we really want to migrate plproxy and citext into PG core distribution?
Date: 2008-07-21 20:37:45
Message-ID: 51C53F9B-7B29-44DA-AE67-9E67521E6695@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jul 21, 2008, at 13:19, Andrew Dunstan wrote:

> I was going to write some stuff about citext anyway. Quite apart
> from the above considerations I'm still a bit concerned about its
> performance characteristics. And I'm not sure we really want all the
> baggage that David is proposing to bring along with it. Is it an
> advance to force the regex_replace "i" flag for such a type? I can
> imagine cases where I might want it to sort insensitively, but be
> able to do case sensitive regex ops on it. It's not as if the user
> can't supply the flag. So right now I don't think citext should be
> included, because there are still issues to sort out, if for no
> other reason.

I'm happy to work with folks to get them figured out, but at the end,
there may be some differing opinions. If there's a reference
implementation that could be checked (how does a case-insensitive
collation work in another database?), that would be fine.

You can use the "c" flag to get case-sensitive comparison with the
regex functions, though not with the operators. (Maybe this should be
moved to a separate thread?)

Best,

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2008-07-21 20:38:35 Re: Do we really want to migrate plproxy and citext into PG core distribution?
Previous Message Tom Lane 2008-07-21 20:33:55 Re: [HACKERS] Hint Bits and Write I/O