Postgres Pro
Downloads
Home   >   mailing lists

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

From Robert Haas
Subject Re: Invalid byte sequence for encoding "UTF8", caused due to non wide-char-aware downcase_truncate_identifier() function on WINDOWS
Date
Msg-id BANLkTi=JzhxzqSzqihS_zF_Tv13iM-3mQw@mail.gmail.com
Whole thread Raw
In response to Re: Invalid byte sequence for encoding "UTF8", caused due to non wide-char-aware downcase_truncate_identifier() function on WINDOWS  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Invalid byte sequence for encoding "UTF8", caused due to non wide-char-aware downcase_truncate_identifier() function on WINDOWS
List pgsql-hackers
Tree view 
On Thu, Jun 9, 2011 at 2:58 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> Right.  Understood.  So let's look at the cases (from git grep
>> pg_strcasecmp and pg_strncasecmp):
>
> Also pg_toupper and pg_tolower.  Right offhand, it looks like psql
> *does* assume it can lower-case identifiers this way :-(

Blarg.  I dunno what to do about that - but surely we must have the
encoding available somewhere?

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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Invalid byte sequence for encoding "UTF8", caused due to non wide-char-aware downcase_truncate_identifier() function on WINDOWS
Next
From: Tom Lane
Date:
Subject: Re: Postmaster holding unlinked files for pg_largeobject table