Re: What about Perl autodie? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: What about Perl autodie?
Date
Msg-id 1914220.1707611796@sss.pgh.pa.us
Whole thread Raw
In response to Re: What about Perl autodie?  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> On 2024-02-08 Th 11:08, Daniel Gustafsson wrote:
>> On 8 Feb 2024, at 16:53, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> 2. Don't wait, migrate them all now.  This would mean requiring
>>> Perl 5.10.1 or later to run the TAP tests, even in back branches.
>>> I think #2 might not be all that radical.  We have nothing older
>>> than 5.14.0 in the buildfarm, so we don't really have much grounds
>>> for claiming that 5.8.3 will work today.  And 5.10.1 came out in
>>> 2009, so how likely is it that anyone cares anymore?

>> I would vote for this option, if we don't run the trailing edge anywhere where
>> breakage is visible to developers then it is like you say, far from guaranteed
>> to work.

> +1 from me too. We kept 5.8 going for a while because it was what the
> Msys (v1) DTK perl was, but that doesn't matter any more I think.

I've reconfigured longfin, which was using perl 5.14.0 on all
branches, to use 5.10.1 on the pre-v16 branches (and it did pass).
This seems like a good change even if we don't pull the trigger on
the above proposal --- although if we don't, maybe I should see
if I can get 5.8.3 to build on that machine.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Sequence Access Methods, round two
Next
From: Noah Misch
Date:
Subject: 035_standby_logical_decoding unbounded hang