Announcing Release 6 of PostgreSQL Buildfarm client

PostgreSQL Buildfarm client Release 6 is now available and can be
downloaded from
<https://buildfarm.postgresql.org/downloads/releases/build-farm-6.tgz>

Features

* use a persistent cache for configure, leading to a substantial
performance improvement for that step, based on an idea from Tom Lane
* improve installcheck security, mirroring earlier changes on this in
Postgres itself
* allow skipping individual TAP tests, e,g, "--skip_steps=pg_dump-check"
* a use_installcheck_parallel setting that uses the parallel schedule
rather than the serial schedule for the installcheck step (not for MSVC)
* use_valgrind and valgrind_options settings that will cause the
installed postmaster to be run under valgrind and report any output.
This doesn't apply to the check step, TAP tests, or any other steps
not using the postmaster started by the start_db step.
* change the default git target for new repos to use https rather than
git protocol
* get PROVE_FLAGS from the environment (can be set in config file)ok,
allowing the overriding of the buildfarm default
* include Redis_FDW and Blackhole_FDW example modules, not enabled by
default.
* new --schedule switch allowing the specification of an alternative
schedule file for the installcheck stage
* new --tests switch allowing for running a specified set of tests
rather than a schedule file at the installcheck stage
* adjust for recent changes in locations of various files such as logs
and regression outputs
* include application name in default log_line_prefix

There have also been a number of fairly minor bug fixes and changes, and
some fairly significant code reorganization and refactoring.

Some manual changes are advised.

First, buildfarm owners are advised to change their config files to add
%q%a to the log_line_prefix setting, if they haven't done so. There is
an example in build-farm.conf.sample:

extra_config =>{
        DEFAULT => [
            q(log_line_prefix = '%m [%p:%l] %q%a '),
            "log_connections = 'true'",
            "log_disconnections = 'true'",
            "log_statement = 'all'",
            "fsync = off"
        ],
},

Also, if you have existing repos using the git protocol, you can change
them to use https by changing the appropriate line in the repo's config
file, so

url = git://git.postgresql.org/git/postgresql.git

would become

url = https://git.postgresql.org/git/postgresql.git

Enjoy

cheers

andrew

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