Re: A mb problem in PostgreSQL

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: cch(at)cc(dot)kmu(dot)edu(dot)tw
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: A mb problem in PostgreSQL
Date: 2000-12-07 04:47:10
Message-ID: 20001207134710R.t-ishii@sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Chih-Chang,

> Do you remember the mb problem about Big5?

Sure.

> Now I have tested all Big5 chars (with ETen extension -- some chars in
> CNS 11643-1992 Plane 3) by the program in the attachment on
> PostgreSQL 7.0.3 with patches from you show me.
> The execution result is also in the attachment.
> The first two insertion fails are normal, because these two chars are
> duplicated in Big5.
> But the 3rd Big5 char (0xF9DC <- > CNS Plane3 0x4B5C) insertion
> is failed. I have no idea about why it is a "Unterminated quoted
> string".
> Could you see where the problem is?

Thanks for the testing effort!

Please apply following one-line-patch and test it again. If it's ok, I
will commit it to both current and stable trees.
--
Tatsuo Ishii

*** postgresql-7.0.3/src/backend/utils/mb/big5.c~ Thu May 27 00:19:54 1999
--- postgresql-7.0.3/src/backend/utils/mb/big5.c Thu Dec 7 13:39:01 2000
***************
*** 322,328 ****
if (b2c3[i][0] == big5)
{
*lc = LC_CNS11643_3;
! return (b2c3[i][1]);
}
}

--- 322,328 ----
if (b2c3[i][0] == big5)
{
*lc = LC_CNS11643_3;
! return (b2c3[i][1] | 0x8080U);
}
}

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-12-07 04:48:57 Re: beta testing version
Previous Message Tom Lane 2000-12-07 04:47:08 Re: HeapTuple?