From: | "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp> |
---|---|
To: | "Clemens Schwaighofer" <cs(at)tequila(dot)co(dot)jp>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Question for Postgres 8.3 |
Date: | 2008-02-05 02:47:26 |
Message-ID: | 09a601c867a1$71155c40$0301a8c0@HP22720319231 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi.
----- Original Message -----
From: "Clemens Schwaighofer" <cs(at)tequila(dot)co(dot)jp>
> hi,
>
> on the page: <http://www.postgresql.org/docs/8.3/static/release-8-3.html>
>
> in point E.1.2.3:
>
> * Disallow database encodings that are inconsistent with the server's
> locale setting (Tom)
>
> does this mean, if my server LOCALE is for example UTF-8.en_US, and I want
> to create a EUC_JP database it gets rejected? do I missunderstand that?
>
> Normaly my servers have default locale set to UTF-8.en_US but also have the
> locales for UTF-8.ja_JP and EUC_JP there, 99.9% of my databases are utf-8,
> but I have some clients that created EUC_JP databases, will the upgrade
> affect this?
When using server encoding for EUC_JP and UTF-8 simultaneously, it is not allowed
except LOCALE=C. Moreover, it can also use SQL_ASCII satisfactory natural.
please initdb --no-locale.
Regards,
Hiroshi Saito
From | Date | Subject | |
---|---|---|---|
Next Message | bh yuan | 2008-02-05 03:18:32 | question about PANIC: hash table "Shared Buffer Lookup Table" corrupted |
Previous Message | Clemens Schwaighofer | 2008-02-05 02:44:34 | Re: Question for Postgres 8.3 |