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

Re: [BUGS] BUG #2120: Crash when doing UTF8<->ISO_8859_8

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: ishii(at)sraoss(dot)co(dot)jp, pgman(at)candle(dot)pha(dot)pa(dot)us, sagi(at)adamnet(dot)co(dot)il,pgsql-patches(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #2120: Crash when doing UTF8<->ISO_8859_8
Date: 2005-12-24 00:27:23
Message-ID: (view raw or whole thread)
Lists: pgsql-bugspgsql-patches
> Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> writes:
> > I think the current implementaion in utf8_and_iso8859.c is fast but
> > too fragile against rearranging of encoding id. I modify those functions
> > in utf8_and_iso8859.c to do a linear search with encoding id.
> That's not unreasonable, but I was wondering whether we could add some
> Assert() tests that would catch problems without imposing any extra cost
> in normal non-Assert builds.

I thought about that too. But my conclusion was current code is too
hard to maintain even if appropreate comments are written in related
Tatsuo Ishii
SRA OSS, Inc. Japan

In response to

pgsql-bugs by date

Next:From: TonyDate: 2005-12-24 19:43:45
Subject: BUG #2125: SELECT problem with strings containing \
Previous:From: Tom LaneDate: 2005-12-23 22:38:05
Subject: Re: horology regression test failure

pgsql-patches by date

Next:From: Peter EisentrautDate: 2005-12-24 11:22:31
Subject: Re: default resource limits
Previous:From: Andrew DunstanDate: 2005-12-23 23:58:22
Subject: Re: [PATCHES] default resource limits

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