diff --git a/doc/src/sgml/regress.sgml b/doc/src/sgml/regress.sgml
index 70d9bdefe1b..6a27aae3195 100644
--- a/doc/src/sgml/regress.sgml
+++ b/doc/src/sgml/regress.sgml
@@ -390,12 +390,37 @@ make check LANG=C ENCODING=EUC_JP
Custom Server Settings
- Custom server settings to use when running a regression test suite can be
+ There are several ways to use custom server settings when running a test
+ suite. This can be useful to enable additional logging, adjust resource
+ limits, or enable extra run-time checks such as . But note that not all tests can be
+ expected to pass cleanly with arbitrary settings.
+
+
+
+ Extra options can be passed to the various initdb
+ commands that are run internally during test setup using the environment
+ variable PG_TEST_INITDB_EXTRA_OPTS. For example, to run a
+ test with checksums enabled and a custom WAL segment size and
+ work_mem setting, use:
+
+make check PG_TEST_INITDB_EXTRA_OPTS='-k --wal-segsize=4 -c work_mem=50MB'
+
+
+
+
+ For the core regression test suite and other tests driven by
+ pg_regress, custom run-time server settings can also be
set in the PGOPTIONS environment variable (for settings
- that allow this):
+ that allow this), for example:
make check PGOPTIONS="-c debug_parallel_query=regress -c work_mem=50MB"
+ (This makes use of functionality provided by libpq; see for details.)
+
+
+
When running against a temporary installation, custom settings can also be
set by supplying a pre-written postgresql.conf:
@@ -405,11 +430,6 @@ make check EXTRA_REGRESS_OPTS="--temp-config=test_postgresql.conf"
-
- This can be useful to enable additional logging, adjust resource limits,
- or enable extra run-time checks such as .
-