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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [COMMITTERS] pgsql: Clean up Perl code according to perlcritic
Дата
Msg-id 14575.1490652977@sss.pgh.pa.us
обсуждение исходный текст
Ответы Re: [COMMITTERS] pgsql: Clean up Perl code according to perlcritic
Список pgsql-hackers
Peter Eisentraut <peter_e@gmx.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@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'
LANGUAGEC 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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Fabien COELHO
Дата:
Сообщение: Re: \if, \elseif, \else, \endif (was Re: PSQL commands:\quit_if, \quit_unless)
Следующее
От: Alexey Kondratov
Дата:
Сообщение: Re: GSOC'17 project introduction: Parallel COPY executionwith errors handling