Re: Fix pg_wchar_tbl.maxmblen

From: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: pgsql-patches(at)postgresql(dot)org
Subject: Re: Fix pg_wchar_tbl.maxmblen
Date: 2007-03-23 03:01:44
Message-ID: 20070323115809.635F.ITAGAKI.TAKAHIRO@oss.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches


ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> wrote:

> I found wrong definitions of max bytes for a char in
> EUC_CN (3->2), EUC_TW (3->4) and MULE_INTERNAL (3->4).

Also, the length of a char in GB18030 could be 4,
though GB18030 is not supported as a server encoding.

- {0, pg_gb18030_mblen, pg_gb18030_dsplen, pg_gb18030_verifier, 2} /* 37; PG_GB18030 */
+ {0, pg_gb18030_mblen, pg_gb18030_dsplen, pg_gb18030_verifier, 4} /* 37; PG_GB18030 */

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2007-03-23 03:16:30 Cleanup to procarray.c
Previous Message ITAGAKI Takahiro 2007-03-23 02:23:13 Fix pg_wchar_tbl.maxmblen