Michael Brusser <[EMAIL PROTECTED]> writes:
> I looked into table pg_conversion - it's empty.
We've seen that reported before. IIRC, it is possible to have
dynamic-linking problems with loading the pg_conversion support
libraries, and the 7.3 version of initdb has a bad habit of sending
the resul
With Pg 7.3.x we initialize database with -E UNICODE option.
I'd like to provide support for automatic conversion to Chinese char-set
by putting "client_encoding big5" into postgresql.conf.
But when I try "\encoding big5" in psql session I get this:
big5: invalid encoding name or conversion proced
