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 Tom Lane
Subject Re: Invalid byte sequence for encoding "UTF8", caused due to non wide-char-aware downcase_truncate_identifier() function on WINDOWS
Date
Msg-id 12612.1307645920@sss.pgh.pa.us
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  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Invalid byte sequence for encoding "UTF8", caused due to non wide-char-aware downcase_truncate_identifier() function on WINDOWS
List pgsql-hackers
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 :-(
        regards, tom lane


pgsql-hackers by date:

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