Re: A mb problem in PostgreSQL - Mailing list pgsql-hackers

From Chih-Chang Hsieh
Subject Re: A mb problem in PostgreSQL
Date
Msg-id 3A3187A8.F9C5F9B7@cc.kmu.edu.tw
Whole thread Raw
In response to Re: A mb problem in PostgreSQL  (Tatsuo Ishii <t-ishii@sra.co.jp>)
Responses Re: Re: A mb problem in PostgreSQL  (Tatsuo Ishii <t-ishii@sra.co.jp>)
Re: Re: A mb problem in PostgreSQL  (Tatsuo Ishii <t-ishii@sra.co.jp>)
List pgsql-hackers
Tatsuo,

Tatsuo Ishii 寫道:

> Please apply following one-line-patch and test it again. If it's ok, I
> will commit it to both current and stable trees.
>
> !                               return (b2c3[i][1] | 0x8080U);

Yes, it's OK. Thank you!
But I wonder why we need to "| 0x8080U"?
b2c3[][] and BIG5toCNS()'s return value are both unsigned short,  aren't they?

--
Chih-Chang Hsieh





pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug in index scans with Locale support enabled
Next
From: mlw
Date:
Subject: Re: OK, does anyone have any better ideas?