pgsql: Ensure plperl strings are always correctly UTF8 encoded.

Started by Andrew Dunstanover 14 years ago3 messagescomitters
Jump to latest
#1Andrew Dunstan
andrew@dunslane.net

Ensure plperl strings are always correctly UTF8 encoded.

Amit Khandekar and Alex Hunsaker.

Backpatched to 9.1 where the problem first occurred.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/4cdb41b54e432ee75e3c61e990b735b15fa66e81

Modified Files
--------------
src/pl/plperl/GNUmakefile | 2 +-
src/pl/plperl/expected/plperl.out | 10 ++++++++++
src/pl/plperl/plperl_helpers.h | 13 ++++++++++++-
src/pl/plperl/sql/plperl.sql | 9 +++++++++
4 files changed, 32 insertions(+), 2 deletions(-)

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Andrew Dunstan (#1)
Re: pgsql: Ensure plperl strings are always correctly UTF8 encoded.

Andrew Dunstan <andrew@dunslane.net> writes:

Ensure plperl strings are always correctly UTF8 encoded.
Amit Khandekar and Alex Hunsaker.

This patch broke the buildfarm members that don't support multiple Perl
interpreters, apparently because of an entirely random decision about
which plperl variant to test where.

regards, tom lane

#3Andrew Dunstan
andrew@dunslane.net
In reply to: Tom Lane (#2)
Re: pgsql: Ensure plperl strings are always correctly UTF8 encoded.

On 11/26/2011 06:07 PM, Tom Lane wrote:

Andrew Dunstan<andrew@dunslane.net> writes:

Ensure plperl strings are always correctly UTF8 encoded.
Amit Khandekar and Alex Hunsaker.

This patch broke the buildfarm members that don't support multiple Perl
interpreters, apparently because of an entirely random decision about
which plperl variant to test where.

Oh, darn. Will fix.

cheers

andrew