Re: BUG #1268: Two different Unicode chars are treated as - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #1268: Two different Unicode chars are treated as
Date
Msg-id 16990.1096000381@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #1268: Two different Unicode chars are treated as  (Kent Tong <kent@cpttm.org.mo>)
Responses Re: BUG #1268: Two different Unicode chars are treated as  (Kent Tong <kent@cpttm.org.mo>)
List pgsql-bugs
Kent Tong <kent@cpttm.org.mo> writes:
> Does it matter? The encoding provided to initdb is just
> a default for the databases to be created in the future.

Yes it does, and you missed the point.  I said *locale*, not *encoding*.
The LC_COLLATE and LC_CTYPE settings that prevail during initdb are
fixed and not alterable without re-initdb.  (I agree that this sucks,
but that's how it is for now...)

Your test program doesn't prove a lot unless you are sure it's executing
under the same locale settings as the postmaster is running in.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Kent Tong
Date:
Subject: Re: BUG #1268: Two different Unicode chars are treated as
Next
From: John Kelly
Date:
Subject: Regression test geometry.out may have wrong value.