Re: Invalid byte sequence for encoding "UTF8", caused due to non wide-char-aware downcase_truncate_identifier() function on WINDOWS

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Invalid byte sequence for encoding "UTF8", caused due to non wide-char-aware downcase_truncate_identifier() function on WINDOWS
Date: 2011-06-09 14:58:58
Message-ID: BANLkTinV-FNwKKFChMNmoZmgrMOtnP45fA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 9, 2011 at 10:38 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Thu, Jun 9, 2011 at 10:15 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> If we need to work around brain-dead isupper() tests, maybe the best
>>> thing is to implement two versions of the loop:
>>>
>>>        if (encoding is single byte)
>>>                ... loop as it stands ...
>>>        else
>>>                ... loop without the "else if" part
>
>> That seems like a clear improvement.  It's a long way from perfect,
>> but still worthwhile.
>
>> Would we back-patch that?  Just do it in master?  Wait for 9.2?
>
> It looks to me like a portability bug fix, so I'd say back-patch.
>
> I'll take care of it, unless you're hot to do so?

Nope, have at it.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-06-09 14:59:54 Re: Autoanalyze and OldestXmin
Previous Message Robert Haas 2011-06-09 14:58:30 Re: Autoanalyze and OldestXmin