| From: | David Wall <d(dot)wall(at)computer(dot)org> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Question for Postgres 8.3 |
| Date: | 2008-02-05 05:31:46 |
| Message-ID: | 47A7F4C2.4020907@computer.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> If you want to support multiple encodings, the only safe locale choice
> is (and always has been) C. If you doubt this, troll the archives for
> awhile --- for example, searching for locale+encoding in pgsql-bugs
> should provide plenty of amusing reading matter.
This is most interesting. I think some of use UTF-8 under the
impression that it would support unicode/java (and thus US-ascii)
easily, and of course then allow for foreign language encodings when we
need to internationalize. Thank goodness we only plan to I18N for a
decade and never got around to it!
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ken Johanson | 2008-02-05 05:37:13 | Re: failed to build any 8-way joins: SQLSTATE: XX000 on PostgreSQL 8.2.6 |
| Previous Message | Tom Lane | 2008-02-05 05:00:03 | Re: failed to build any 8-way joins: SQLSTATE: XX000 on PostgreSQL 8.2.6 |