Re: BUG #13638: Exception texts from plperl has bad encoding

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, lei(at)aswsyst(dot)cz, pgsql-bugs(at)postgresql(dot)org, Alex Hunsaker <badalex(at)gmail(dot)com>
Subject: Re: BUG #13638: Exception texts from plperl has bad encoding
Date: 2015-09-27 23:46:19
Message-ID: 13303.1443397579@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com> writes:
> I think you want to call croak_sv(SV) with an SV containing the error
> message and flagged as UTF-8.

I found croak_sv() in the headers for Perl 5.18 (present on OS X Yosemite)
but not in Perl 5.10 (present on RHEL6), much less 5.8 which is the oldest
Perl version we claim to support. This doesn't look like a workable
answer unless we want to move the compatibility goalposts a long way.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alex Hunsaker 2015-09-28 00:20:23 Re: BUG #13638: Exception texts from plperl has bad encoding
Previous Message Amir Rohan 2015-09-27 22:36:44 Re: BUG #13643: Should a process dying bring postgresql down, or not?