Re: Re: [COMMITTERS] pgsql: Force strings passed to and from plperl to be in UTF8 encoding.
От | Andrew Dunstan |
---|---|
Тема | Re: Re: [COMMITTERS] pgsql: Force strings passed to and from plperl to be in UTF8 encoding. |
Дата | |
Msg-id | 4EB1CE58.2010006@dunslane.net обсуждение исходный текст |
Ответ на | Re: Re: [COMMITTERS] pgsql: Force strings passed to and from plperl to be in UTF8 encoding. (Alex Hunsaker <badalex@gmail.com>) |
Ответы |
Re: Re: [COMMITTERS] pgsql: Force strings passed to and
from plperl to be in UTF8 encoding.
|
Список | pgsql-hackers |
On 10/07/2011 12:51 PM, Alex Hunsaker wrote: > On Wed, Oct 5, 2011 at 20:36, Robert Haas<robertmhaas@gmail.com> wrote: >> On Wed, Oct 5, 2011 at 5:03 PM, Alex Hunsaker<badalex@gmail.com> wrote: >>> On Wed, Oct 5, 2011 at 08:18, Robert Haas<robertmhaas@gmail.com> wrote: >>>> On Wed, Oct 5, 2011 at 3:58 AM, Amit Khandekar >>>> <amit.khandekar@enterprisedb.com> wrote: >>>>> I have no more issues with the patch. >>>>> Thanks! >>>> I think this patch needs to be added to the open CommitFest, with >>>> links to the reviews, and marked Ready for Committer. >>> The open commitfest? Even if its an "important" bug fix that should be >>> backpatched? >> Considering that the issue appears to have been ignored from >> mid-February until early October, I don't see why it should now get to >> jump to the head of the queue. Other people may have different >> opinions, of course. > Added. :-) > I'm just starting to look at this, by way of a break in staring at pg_dump code ;-). This just needs to be backpatched to 9.1, is that right? cheers andrew
В списке pgsql-hackers по дате отправления: