> not easy to find ...). After re-compiling with "--with-mb" and
Sorry for the inconvenience. I would like to write docs for the
multi-byte support in PostgreSQL for the next release.
> "--enable-locale", re-creating the data directory with "initdb -e
> LATIN1" and re-building my database with "-e LATIN1" as well, I'm able
> e.g. to get +-proper sorting of strings with German umlauts
> etc.
>
> However, when I try to use the precompiled psql client for Windows
> from "ftp://ftp.postgresql.org" over a network connection, it is not
I am not sure the binary being compiled with mb.
> able to understand the "special" characters like "u umlaut" etc.,
> whether I set CLIENT_ENCODING to either 'WIN', 'ALT', or 'LATIN1' (I
> think, multibyte support is compiled in the client, at least my unix
> psql won't let me set this variable if it has no mb).
Sounds strange. I assume you use "set client encoding to 'LATIN1'" or
something like that. It is just a query for psql, since psql doesn't
parse the contents of the query, it should be possible for non-mb psql
to send the query.
Anyway, to make sure that you are using mb enabled psql, start
postmaster with "-d 3" flag to get debug output (turn off -
S. otherwise debug out will not appear). You should get lots of
messages including following portions:
query: select getdatabaseencoding()
ProcessQuery
CommitTransactionCommand
StartTransactionCommand
query: SET client_encoding = 'LATIN1'
ProcessUtility: SET client_encoding = 'LATIN1'
If not, you gotta into trouble. You need to build mb enabled psql on
PC by yourself. Unfortunately I cannot make it for you, since I have
very little knowledges about Windows. Maybe Hiroki Kataoka have some
suggestions...
--
Tatsuo Ishii