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

From Alex Hunsaker
Subject Re: BUG #13638: Exception texts from plperl has bad encoding
Date
Msg-id CAFaPBrQahL89XxHELtKn3eNtuirTijDc91bUFZQH4BXvvC+Nyg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #13638: Exception texts from plperl has bad encoding  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Tue, Sep 29, 2015 at 8:55 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> 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, [...]
>
> 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
>

I've been keeping a loose eye on the buildfarm, everything looks good so
far.

FYI I also ended up testing 5.16.3 and 5.20.3 which means it should be
tested on every stable version of perl.

Thanks!

pgsql-bugs by date:

Previous
From: Maris Radu
Date:
Subject: Re: BUG #13652: Function names as a table prefiex by underscore, confused with array
Next
From: Thomas Munro
Date:
Subject: Re: GRANT USAGE ON SEQUENCE missing from psql command completion