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

From Tim Bunce
Subject Re: BUG #13638: Exception texts from plperl has bad encoding
Date
Msg-id 20150927141148.GA1416@timac.local
Whole thread Raw
In response to Re: BUG #13638: Exception texts from plperl has bad encoding  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: BUG #13638: Exception texts from plperl has bad encoding  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Fri, Sep 25, 2015 at 04:51:20PM -0300, Alvaro Herrera wrote:
> Tom Lane wrote:
>
> > It's still beyond my Perl-fu ...
>
> Maybe Alex or Tim can shed some light?  Please see:
> http://www.postgresql.org/message-id/flat/20150925112345.26913.28407@wrigleys.postgresql.org

I think you want to call croak_sv(SV) with an SV containing the error
message and flagged as UTF-8.

Yim.

pgsql-bugs by date:

Previous
From: Amir Rohan
Date:
Subject: Re: BUG #13642: no backup_label file in PG_DATA after pg_stop_backup();
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #13643: Should a process dying bring postgresql down, or not?