From: | Alex Hunsaker <badalex(at)gmail(dot)com> |
---|---|
To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, alvherre(at)commandprompt(dot)com, cb(at)df7cb(dot)de, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pl/perl and utf-8 in sql_ascii databases |
Date: | 2012-07-06 01:56:11 |
Message-ID: | CAFaPBrTMRO=h=Eqn-2PQ3z36JWhayAuWOKgj7zZe7p5U9ahjqA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jul 3, 2012 at 2:59 AM, Kyotaro HORIGUCHI
<horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> Hello, Here is regression test runs on pg's also built with
> cygwin-gcc and VC++.
Thank you!
> The patches attached following,
>
> - plperl_sql_ascii-4.patch : fix for pl/perl utf8 vs sql_ascii
> - plperl_sql_ascii_regress-1.patch : regression test for this patch.
> I added some tests on encoding to this.
>
> I will mark this patch as 'ready for committer' after this.
Both patches look good to me..
> I've been stuck in mud trying to plperl work on windows
> environment. I saw many messages complaining that plperl wouldn't
> be built to work. For the convenience of those and myself, I
> describe the process of building postgresql with plperl on
> Windows with cygwin and VC++ I've done below.
Hrm, I don't develop on windows here, but out of curiosity, what were
the messages like?
>> - The remainder of the patch whic fixes the easy fixable leakes
>> of palloc'ed memory won't be ported into 9.1. This is only for
>> 9.3dev.
> What should I do for this?
Just let the commiter decide? :-)
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-07-06 03:45:39 | Re: Event Triggers reduced, v1 |
Previous Message | Josh Kupershmidt | 2012-07-06 01:43:09 | Re: autocomplete - SELECT fx |