From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Per-column collation |
Date: | 2010-12-12 22:13:40 |
Message-ID: | 1292192020.15408.9.camel@vanquo.pezone.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On mån, 2010-12-06 at 21:26 +0200, Peter Eisentraut wrote:
>
> > * contrib/citext raises an encoding error when COLLATE is specified
> > even if it is the collation as same as the database default.
> > We might need some special treatment for C locale.
> > =# SHOW lc_collate; ==> C
> > =# SELECT ('A'::citext) = ('a'::citext); ==> false
> > =# SELECT ('A'::citext) = ('a'::citext) COLLATE "C";
> > ERROR: invalid multibyte character for locale
> > HINT: The server's LC_CTYPE locale is probably incompatible with
> the
> > database encoding.
>
> OK, I can reproduce that. That's fallout from the lc_ctype_is_c()
> optimization that I removed, as explained in another email. I'll have
> to think about that again.
This is fixed in the 20101213 patch I'm about to send out.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2010-12-12 22:15:01 | Re: Per-column collation |
Previous Message | Peter Eisentraut | 2010-12-12 22:12:40 | Re: Per-column collation |