Re: error message diff with Perl 5.22.0

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: error message diff with Perl 5.22.0
Date: 2015-06-11 00:10:10
Message-ID: 5578D1E2.2000503@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6/6/15 10:32 PM, Alvaro Herrera wrote:
> Peter Eisentraut wrote:
>> With the recently released Perl 5.22.0, the tests fail thus:
>>
>> -ERROR: Global symbol "$global" requires explicit package name at line 3.
>> -Global symbol "$other_global" requires explicit package name at line 4.
>> +ERROR: Global symbol "$global" requires explicit package name (did you forget to declare "my $global"?) at line 3.
>> +Global symbol "$other_global" requires explicit package name (did you forget to declare "my $other_global"?) at line 4.
>> CONTEXT: compilation of PL/Perl function "uses_global"
>>
>>
>> With PL/Python, this happens for just about every other release, and we usually add another expected file. I don't see anything like that for PL/Perl yet. Should we add a new expected file, or is there a different preferred solution?
>
> How many .sql files does this affect? Alternate expected output is
> bothersome; if more than one test file is affected, I think the best is
> to isolate the cases where this appears to a single .sql file, as short
> as possible, so that we don't have to touch it for anything else, and so
> that we don't have to touch the isolated file except for similar
> changes.

It's only one file.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2015-06-11 01:15:13 Re: [idea] table partition + hash join
Previous Message Andrew Dunstan 2015-06-10 23:55:15 Re: jsonb - path