On Thu, Jul 2, 2015 at 11:56 AM, Tom Lane wrote:
> Alex Hunsaker writes:
>> (What about the back branches? :D)
>
> Indeed. dangomushi is complaining about this in the back branches now.
Yep, perl 5.22 is used there.
--
Michael
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql
Alex Hunsaker writes:
> (What about the back branches? :D)
Indeed. dangomushi is complaining about this in the back branches now.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.p
On Sat, Jun 6, 2015 at 7:03 PM, 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
Peter Eisentraut writes:
> 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 packa
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:
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 pack
Alvaro Herrera wrote:
> Also, do we need a buildfarm member running 5.22?
Actually, I wonder if there's a way to have a buildfarm animal that runs
the pl/perl tests with all supported versions of Perl, for example.
This would probably require adding a new .pm file each time a new Perl
is released