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

Re: BUG #2120: Crash when doing UTF8<->ISO_8859_8 encoding

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: ishii(at)sraoss(dot)co(dot)jp
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, sagi(at)adamnet(dot)co(dot)il, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #2120: Crash when doing UTF8<->ISO_8859_8 encoding
Date: 2005-12-22 05:11:45
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugspgsql-patches
> > "Sagi Bashari" <sagi(at)adamnet(dot)co(dot)il> writes:
> > > Postgresql crashes when a client with ISO_8859_8 encoding tries to select
> > > data from a utf8 database.
> > 
> > It looks like somebody rearranged the pg_enc enum without bothering to
> > fix the tables that are affected by this.
> > 
> > utf8_and_iso8859.c is certainly broken, and I'm wondering what else
> > might be.  Tatsuo, can you think of any other places to look?
> I will look into this.

Quick check reveals that ISO-8859-5 to ISO-8859-8 are broken.
Tatsuo Ishii
SRA OSS, Inc. Japan

In response to

pgsql-bugs by date

Next:From: Martin PittDate: 2005-12-22 07:25:39
Subject: Re: horology regression test failure
Previous:From: Bruce MomjianDate: 2005-12-22 03:29:02
Subject: Re: [HACKERS] Better path-matching for package relocatability (was Re:

pgsql-patches by date

Next:From: Manuel SugawaraDate: 2005-12-22 05:50:06
Subject: Re: to_char and i18n
Previous:From: Gavin SherryDate: 2005-12-22 05:10:00
Subject: Re: to_char and i18n

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