> On Tue, Aug 28, 2001 at 06:03:55PM +0800, Michael R. Fahey wrote: > > I compiled 7.1.3 with configure --multibyte=UNICODE and > > --enable-unicode-conversion (Red Hat Linux 6.1, Kernel 2.2.19). > > > > Now I'm trying to follow the instructions given by Tatsuo Ishii in his > > 18 March 2001 post on how to convert big5. But createdb -E UNICODE > > unicode fails with the message > > > > ERROR: Multi-byte support is not enabled. You have multibyte disabled backend somewhere. If you have not made a mistake in cut&paste your configure command, it should be: configure --enable-multibyte=UNICODE not: configure --multibyte=UNICODE > > Also, in psql \encoding BIG5 fails with the message > > > > BIG5: invalid encoding name. This might be caused above. > The 'BIG5' is client encoding only. PG can on the fly encode > data from some multibyte (unicode, mule_internal) encoding > used for server to big5 used on client, but you can't directly > use big5 at server (DB). No. \encoding command sets the client encoding, not DB encoding. So "\encoding BIG5" is a valid command in his case. -- Tatsuo Ishii ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
