Re: pgsql: Silence perlcritic warning about missing return.

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Silence perlcritic warning about missing return.
Date: 2018-10-21 12:18:14
Message-ID: 2985c393-ea0f-b1da-4729-e778ee84ff06@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 10/19/2018 11:43 PM, Michael Paquier wrote:
> On Fri, Oct 19, 2018 at 06:00:26PM +0000, Tom Lane wrote:
>> Silence perlcritic warning about missing return.
>>
>> Per buildfarm member crake.
> Thanks! I did not know that this was run automatically.

It's been running since we improved our perlcritic coverage. Someone
complained that we wouldn't know when we caused a breach of the policy,
so I fixed that :-)

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2018-10-21 13:03:35 pgsql: Don't try to test files named with a trailing dot on Windows
Previous Message Andrew Dunstan 2018-10-20 13:17:18 pgsql: Lower privilege level of programs calling regression_main