> Hm, it would seem that for some reason CLIENT_ENCODING is getting set to
> LATIN2. Digging in the code, the only reason I can find for that to
> happen within initdb is if you have set PGCLIENTENCODING as an
> environment variable in your shell.
Yes, you're right. Thank you very much.
> If you want to use LATIN2 as your client encoding, it'd probably be a
> good idea not to use UNICODE as the database encoding ...
LATIN2 encoding is only on server (RH 7.2 now, Fedora in few months).
But there is WIN1250 encoding on most clients. Is UNICODE such
speed down? I think (but I'm not sure) it's better to choose UNICODE
and have less problems in the future.
Luf
