Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Re: [BUGS] Problems in 6.5.3 with Multi-Byte encoding

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>
Cc: Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Re: [BUGS] Problems in 6.5.3 with Multi-Byte encoding
Date: 1999-11-20 12:05:26
Message-ID: 199911201205.VAA05702@srapc451.sra.co.jp (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
> I have another kind of problem related with MB and 6.5.3.
> 
> On FreeBSD 3.1:
[snip]
> It's interesting that on Linux I have no problem.
> I have no time right now to test 6.5.2 but I recall I had no
> such problem (not 100% sure).

I think no change has been made between 6.5.2 and 6.5.3 regarding MB.
Can you send me the KOI8 data and WIN data that is supposed to be
correct? I will check it out on a FreeBSD 3.2 machine.

> > With PostgreSQL compiled with support for locales and multi-byte encoding:
> > 
> > initdb -e BIG5

No, you cannot do this. If you want to use traditional Chinese, you
have to make a database with EUC_TW (initdb -e EUC_TW) then set the
PGCLIENTENCODING environment variable to BIG5 on the client side. See
doc/README.mb for more details.

Maybe initdb should reject BIG5. I will do it in for the next release.
---
Tatsuo Ishii

pgsql-hackers by date

Next:From: C.S.ParkDate: 1999-11-20 13:26:16
Subject: [q] can I simply remove pg_log file?
Previous:From: Bruce MomjianDate: 1999-11-20 04:23:13
Subject: 7.0 status request

pgsql-bugs by date

Next:From: nateDate: 1999-11-23 04:05:41
Subject: postmaster crashing on semi large tabl
Previous:From: Oleg BartunovDate: 1999-11-19 11:19:00
Subject: Re: [BUGS] Problems in 6.5.3 with Multi-Byte encoding

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group