Re: Make all Perl warnings fatal

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Make all Perl warnings fatal
Date: 2024-01-18 07:52:33
Message-ID: eadafe5e-a2be-44c1-95a6-6a8308b0fb7a@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 16.01.24 12:08, Bharath Rupireddy wrote:
> On Fri, Jan 12, 2024 at 9:21 PM Bharath Rupireddy
> <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>>
>> On Fri, Jan 12, 2024 at 9:03 PM Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>>>
>>> I would put this code
>>>
>>> my $core = $ret & 128 ? " (core dumped)" : "";
>>> die "psql exited with signal "
>>> . ($ret & 127)
>>> . "$core: '$$stderr' while running '@psql_params'"
>>> if $ret & 127;
>>> $ret = $ret >> 8;
>>>
>>> inside a if (defined $ret) block.
>>>
>>> Then the behavior would be that the whole function returns undef on
>>> timeout, which is usefully different from returning 0 (and matches
>>> previous behavior).
>>
>> WFM.
>
> I've attached a patch for the above change.

Committed, thanks.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2024-01-18 07:59:20 Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features)
Previous Message Jeff Davis 2024-01-18 07:17:01 Re: [17] CREATE SUBSCRIPTION ... SERVER