Re: Make all Perl warnings fatal - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Make all Perl warnings fatal
Date
Msg-id 0e7c7c7c-4a67-4550-a36d-a9fcd8aa8489@eisentraut.org
Whole thread Raw
In response to Re: Make all Perl warnings fatal  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: Make all Perl warnings fatal
List pgsql-hackers
On 22.12.23 22:33, Peter Eisentraut wrote:
> On 12.09.23 07:42, Peter Eisentraut wrote:
>> On 10.08.23 07:58, Peter Eisentraut wrote:
>>> There are also a couple of issues in the MSVC legacy build system 
>>> that would need to be tightened up in order to survive with fatal 
>>> Perl warnings.  Obviously, there is a question whether it's worth 
>>> spending any time on that anymore.
>>
>> It looks like there are no principled objections to the overall idea 
>> here, but given this dependency on the MSVC build system removal, I'm 
>> going to set this patch to Returned with feedback for now.
> 
> Now that that is done, here is an updated patch for this.
> 
> I found one more bug in the Perl code because of this, a fix for which 
> is included here.
> 
> With this fix, this passes all the CI tests on all platforms.

committed



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: Schema variables - new implementation for Postgres 15
Next
From: Tom Lane
Date:
Subject: Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs