Re: CURRENT CVS: MULTIBYTE: CANT CONNECT....
От | Karel Zak |
---|---|
Тема | Re: CURRENT CVS: MULTIBYTE: CANT CONNECT.... |
Дата | |
Msg-id | 20010908102938.B6888@zf.jcu.cz обсуждение исходный текст |
Ответ на | CURRENT CVS: MULTIBYTE: CANT CONNECT.... (Larry Rosenman <ler@lerctr.org>) |
Список | pgsql-hackers |
On Fri, Sep 07, 2001 at 09:06:18PM -0500, Larry Rosenman wrote: > I finally got all the way through a compile set: > > CC=cc CXX=CC ./configure --prefix=/usr/local/pgsql --enable-syslog \ > --with-CXX --with-perl --enable-multibyte --enable-cassert \ > --with-includes=/usr/local/include --with-libs=/usr/local/lib \ > --enable-debug \ > --with-tcl --with-tclconfig=/usr/local/lib \ > --with-tkconfig=/usr/local/lib --enable-locale > and when I try to connect to an existing DB, loaded from a pg_dump > from the previous 7.2devel sources, I get: > TRAP: Failed Assertion("!(ClientEncoding):", File: "mbutils.c", Line: > 314) > !(ClientEncoding) (0) [No such file or directory] Interesting. I don't know why, but someting don't call pg_set_client_encoding() before usage encoding routines (maybe libpq don't set client encoding if it's default SQL_ASCII, but I'm almost sure that I check this case). A simple and robus solution is in the begin of mbutils.c set default ClientEncoding to SQL_ASCII (like default DatabaseEncoding). Bruce, can you change it? It's one line change. Again thanks. Karel -- Karel Zak <zakkr@zf.jcu.cz>http://home.zf.jcu.cz/~zakkr/C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz
В списке pgsql-hackers по дате отправления: