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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
Cc: 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 encoding
Date: 2005-12-23 04:38:26
Message-ID: 15856.1135312706@sss.pgh.pa.us (view raw or flat)
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.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: David WheelerDate: 2005-12-23 04:47:07
Subject: BUG #2122: Inconsistent FK Error Messages
Previous:From: Tatsuo IshiiDate: 2005-12-23 01:59:06
Subject: Re: [BUGS] BUG #2120: Crash when doing UTF8<->ISO_8859_8

pgsql-patches by date

Next:From: Volkan YAZICIDate: 2005-12-23 13:29:40
Subject: Re: tuple count and v3 functions in psql for COPY
Previous:From: Christopher Kings-LynneDate: 2005-12-23 02:08:13
Subject: Re: Disparity in search_path SHOW and SET

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