Re: Make all Perl warnings fatal

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Anton Voloshin <a(dot)voloshin(at)postgrespro(dot)ru>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Alexander Korotkov <akorotkov(at)postgresql(dot)org>
Subject: Re: Make all Perl warnings fatal
Date: 2024-10-22 10:26:31
Message-ID: CAPpHfdt16mQno7bBAHsocqnP4joudx+ozAA5GCvqzqrb2eeKmw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi!

On Tue, Oct 22, 2024 at 12:26 PM Anton Voloshin
<a(dot)voloshin(at)postgrespro(dot)ru> wrote:
> On 18/01/2024 10:52, Peter Eisentraut wrote:
> > Committed, thanks.
>
> since this patch two .pl files without FATAL in "use warnings" have been
> committed to master:
> src/test/recovery/t/043_wal_replay_wait.pl
> src/test/modules/test_misc/t/006_signal_autovacuum.pl

Thank you for spotting this.
I have just changed relevant line in 043_wal_replay_wait.pl.

------
Regards,
Alexander Korotkov
Supabase

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2024-10-22 10:50:00 Re: Pgoutput not capturing the generated columns
Previous Message Tatsuo Ishii 2024-10-22 10:19:09 Re: Row pattern recognition