On Jun 6, 2011, at 1:14 PM, Tom Lane wrote:
> The most workable alternative that I can see is to lobotomize citext so
> that it always does lower-casing according to the database's "default"
> collation, which would allow us to pretend that its notion of equality
> is not collation-sensitive after all.
+1 Seems like the right thing to do for now.
> We could hope to improve this in
> future release cycles, but not till we've done the infrastructure work
> outlined above. One bit of infrastructure that might be a good idea is
> a flag to indicate whether an equality operator's behavior is
> potentially collation-dependent, so that we could avoid taking
> performance hits in the normal case.
That sounds like a good idea.
Best,
David
