From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | SAKAIDA Masaaki <sakaida(at)psn(dot)co(dot)jp> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: client libpq multibyte support |
Date: | 2000-05-05 03:40:04 |
Message-ID: | 4504.957498004@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
SAKAIDA Masaaki <sakaida(at)psn(dot)co(dot)jp> writes:
> A client application using libpq made by non-MULTIBYTE
> can not talk to server made by MULTIBYTE.
> admin=# select * from SJIS_KANJI ;
> \: extra argument ';' ignored
> \: extra argument ';' ignored
> Invalid command \. Try \? for help.
Ugh :-(. We have not seen this reported before --- do you know exactly
where it's coming from? (I suspect it may be a psql issue not a libpq
issue, but hard to say without more info.)
> I hope that a client 7.0-libpq and an application always be
> made by "configure --enable-multibyte" even if MULTIBYTE isn't
> necessary for backend. If so, the above problem will be solved.
I do not think that will go over well with people who don't need
multibyte support, since the MULTIBYTE code is a good deal larger
and slower. Also, AFAIK we didn't have any such problem in 6.5, so
perhaps this is just a small bug not requiring such a sledgehammer
solution. We need to look more closely.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-05-05 03:41:13 | Re: [HACKERS] Request for 7.0 JDBC status |
Previous Message | The Hermit Hacker | 2000-05-05 03:36:25 | Re: pg_group_name_index corrupt? |