Re: BUG #13638: Exception texts from plperl has bad encoding - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #13638: Exception texts from plperl has bad encoding
Date
Msg-id 14108.1443538520@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #13638: Exception texts from plperl has bad encoding  (Alex Hunsaker <badalex@gmail.com>)
Responses Re: BUG #13638: Exception texts from plperl has bad encoding
List pgsql-bugs
Alex Hunsaker <badalex@gmail.com> writes:
> On Mon, Sep 28, 2015 at 10:28 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> BTW, I think we can't actually use this regression test case, [...]

> Agreed. I'll attach it separately just for easy verification that
> everything is working as intended.

After awhile I remembered that we already had a similar test case in
plpython: it's testing with no-break space (U+A0) which has an equivalent
in most encodings.  So I adopted that strategy, and pushed this with
a test case.  We'll soon see if the buildfarm likes it.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #13649: system catalog pg_authid doesn't update automatically
Next
From: sivanov99901@gmail.com
Date:
Subject: BUG #13650: getTypeBinaryStringInfo segfault