Skip site navigation (1) Skip section navigation (2)

Re: Re: [COMMITTERS] pgsql: Force strings passed to and from plperl to be in UTF8 encoding.

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Amit Khandekar <amit(dot)khandekar(at)enterprisedb(dot)com>
Cc: Alex Hunsaker <badalex(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Force strings passed to and from plperl to be in UTF8 encoding.
Date: 2011-11-26 17:23:30
Message-ID: 4ED12092.4040100@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers

On 10/05/2011 03:58 AM, Amit Khandekar wrote:
> On 5 October 2011 12:29, Alex Hunsaker<badalex(at)gmail(dot)com>  wrote:
>>
>> Find it attached. [ Note I didn't put the check inside the if (ret ==
>> utf8_str) as it seemed a bit cleaner (indentation wise) to have it
>> outside ]
> I have no more issues with the patch.
>

Committed.

cheers

andrew

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2011-11-26 17:24:10
Subject: Re: [COMMITTERS] pgsql: Modify pg_dump to use error-free memory allocation macros. This
Previous:From: Bruce MomjianDate: 2011-11-26 17:15:39
Subject: Re: [COMMITTERS] pgsql: Modify pg_dump to use error-free memory allocation macros. This

pgsql-committers by date

Next:From: Tom LaneDate: 2011-11-26 17:24:10
Subject: Re: [COMMITTERS] pgsql: Modify pg_dump to use error-free memory allocation macros. This
Previous:From: Andrew DunstanDate: 2011-11-26 17:20:38
Subject: pgsql: Ensure plperl strings are always correctly UTF8 encoded.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group