Tom Lane aae40cf13b Fix plperl to handle non-ASCII error message texts correctly. ... We were passing error message texts to croak() verbatim, which turns out not to work if the text contains non-ASCII characters; Perl mangles their encoding, as reported in bug #13638 from Michal Leinweber. To fix, convert the text into a UTF8-encoded SV first. It's hard to test this without risking failures in different database encodings; but we can follow the lead of plpython, which is already assuming that no-break space (U+00A0) has an equivalent in all encodings we care about running the regression tests in (cf commit 2dfa15de5). Back-patch to 9.1. The code is quite different in 9.0, and anyway it seems too risky to put something like this into 9.0's final minor release. Alex Hunsaker, with suggestions from Tim Bunce and Tom Lane		2015-09-29 10:52:22 -04:00
..
plperl	Fix plperl to handle non-ASCII error message texts correctly.	2015-09-29 10:52:22 -04:00
plpgsql	Fix a few bogus statement type names in plpgsql error messages.	2015-08-18 19:22:38 -04:00
plpython	Fix plpython crash when returning string representation of a RECORD result.	2015-08-21 12:21:37 -04:00
tcl	Fix (some of) pltcl memory usage	2015-07-20 14:18:08 +02:00
Makefile	Make distprep and *clean build targets recurse into all subdirectories.	2011-07-03 13:55:12 -04:00