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

Re: pgsql: Work around for perl 5.10 bug - fix due to perl hacker Simon

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Work around for perl 5.10 bug - fix due to perl hacker Simon
Date: 2008-01-22 23:32:53
Message-ID: 47967D25.2030303@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-committers
I don't actually have a lot of information. Simon told me that, due to a 
change in behaviour which he described as a bug, we need to enable the 
caller opcode during the load of the strict module, and that we could 
turn it off again once the module was imported. That's what I did (after 
testing). It's a tiny and quite safe change. If you like I will add a 
note to the code saying why it's there.

cheers

andrew

Neil Conway wrote:
> More information in the commit message would be good to see (for the
> sake of the CVS history, if nothing else).
>
> -Neil
>
> On Tue, 2008-01-22 at 20:17 +0000, Andrew Dunstan wrote:
>   
>> Log Message:
>> -----------
>> Work around for perl 5.10 bug - fix due to perl hacker Simon Cozens.
>>
>> Modified Files:
>> --------------
>>     pgsql/src/pl/plperl:
>>         plperl.c (r1.134 -> r1.135)
>>         (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plperl/plperl.c?r1=1.134&r2=1.135)
>>
>> ---------------------------(end of broadcast)---------------------------
>> TIP 6: explain analyze is your friend
>>
>>     
>
>
>   

In response to

Responses

pgsql-committers by date

Next:From: Andrew DunstanDate: 2008-01-23 00:55:47
Subject: pgsql: Document the fix for perl 5.10 with this comment: * The
Previous:From: Neil ConwayDate: 2008-01-22 22:43:46
Subject: Re: pgsql: Work around for perl 5.10 bug - fix due toperl hacker Simon

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