Re: [COMMITTERS] pgsql: Clean up Perl code according to perlcritic

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [COMMITTERS] pgsql: Clean up Perl code according to perlcritic
Date: 2017-03-27 22:16:17
Message-ID: 14575.1490652977@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Clean up Perl code according to perlcritic

This seems to have broken the regression tests (specifically, dblink)
on at least some of the Windows buildfarm critters. It looks like
something got changed in the behavior of build-tree path expansion:
this in the input/paths.source file

CREATE FUNCTION putenv(text)
RETURNS void
AS '@libdir@/regress(at)DLSUFFIX@', 'regress_putenv'
LANGUAGE C STRICT;

results in

CREATE FUNCTION putenv(text)
RETURNS void
RETURNS void
AS 'C:/buildfarm/HEAD/pgsql.build/contrib/dblink/$(top_builddir)/src/test/regress/regress.dll', 'regress_putenv'
LANGUAGE C STRICT;
+ ERROR: could not access file "C:/buildfarm/HEAD/pgsql.build/contrib/dblink/$(top_builddir)/src/test/regress/regress.dll": No such file or directory

which is surely not what it ought to be.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-03-28 00:14:41 pgsql: Show ignored constants as "$N" rather than "?" in pg_stat_statem
Previous Message Alvaro Herrera 2017-03-27 17:59:46 pgsql: Fix uninitialized memory propagation mistakes

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexey Kondratov 2017-03-27 22:54:54 Re: GSOC'17 project introduction: Parallel COPY execution with errors handling
Previous Message Fabien COELHO 2017-03-27 21:34:26 Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless)