Horton

Re: [Doc] Tiny fix for regression tests example

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: "tanghy.fnst@fujitsu.com" <tanghy.fnst@fujitsu.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, "peter@eisentraut.org" <peter@eisentraut.org>, Craig Ringer <craig.ringer@2ndquadrant.com>
Date: 2021-07-26T04:04:00Z
Lists: pgsql-hackers, pgsql-docs 
On Fri, Jul 23, 2021 at 06:12:02AM +0000, tanghy.fnst@fujitsu.com wrote:
> Here's a tiny fix in regress.sgml.
> 
> -make check PGOPTIONS="-c log_checkpoints=on -c work_mem=50MB"
> +make check PGOPTIONS="-c geqo=off -c work_mem=50MB"
> 
> log_checkpoints couldn't be set in PGOPTIONS.
> 
> Replace log_checkpoints with geqo in the example code.

Right, that won't work.  What about using something more
developer-oriented here, say force_parallel_mode=regress?

> -make check EXTRA_REGRESS_OPTS="--temp-config=test_postgresql.conf"
> +make check EXTRA_REGRESS_OPTS="--temp-config=$(pwd)/test_postgresql.conf"
> 
> User needs to specify $(pwd) to let the command execute as expected.

This works as-is.
--
Michael

Commits

  1. doc: Fix command example to run regression tests with PGOPTIONS