| From: | Bruce Momjian <bruce(at)momjian(dot)us> | 
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
| Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, pg(at)heroku(dot)com, pgsql-bugs(at)postgresql(dot)org | 
| Subject: | Re: PQclientEncoding() returns -1, resulting in possible assertion failure in psql | 
| Date: | 2014-03-23 00:17:11 | 
| Message-ID: | 20140323001711.GA5606@momjian.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-bugs | 
On Sat, Mar 22, 2014 at 11:55:56AM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > OK, hearing nothing, I dug into this, and I think the solution is
> > simpler than we thought.  Basically, the Assert is checking for the
> > encoding value to be in a valid range, but the main code is also
> > checking for an invalid encoding and returning PG_SQL_ASCII:
> 
> Agreed that that's pretty useless.  I wonder though why these functions
> are not coded like
> 
>        return PG_VALID_ENCODING(encoding) ?
>            ((*pg_wchar_table[encoding].mblen) ((const unsigned char *) mbstr)) :
>            ((*pg_wchar_table[PG_SQL_ASCII].mblen) ((const unsigned char *) mbstr)));
> 
> instead of the hard-to-read explicit range check.
Agreed. Modified patch attached.
-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com
  + Everyone has their own god. +
| Attachment | Content-Type | Size | 
|---|---|---|
| mblen.diff | text/x-diff | 3.1 KB | 
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Haribabu Kommi | 2014-03-24 02:42:22 | Re: BUG #9652: inet types don't support min/max | 
| Previous Message | Tom Lane | 2014-03-22 15:59:13 | Re: PQclientEncoding() returns -1, resulting in possible assertion failure in psql |