| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michal Leinweber <lei(at)aswsyst(dot)cz> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #13638: Exception texts from plperl has bad encoding |
| Date: | 2015-09-25 20:44:07 |
| Message-ID: | 20832.1443213847@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michal Leinweber <lei(at)aswsyst(dot)cz> writes:
> The problem is not only with elog call, but it also fires if plpgsql
> code called from plperl function raises exception.
Hmm, yeah, there are a whole bunch of instances of that croak("%s",
edata->message) pattern, and most of them don't have an ancestral SV
to work from. So we'll need a more general solution anyway, and it
may not be worth changing do_util_elog() to work in a fundamentally
different way than the rest.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-09-25 22:16:50 | Re: BUG #13640: Delete isn't using available Index Only Scan |
| Previous Message | Michal Leinweber | 2015-09-25 20:15:34 | Re: BUG #13638: Exception texts from plperl has bad encoding |