Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit 854434c

Browse files
committed
doc: Document how to run regression tests with custom server settings
Author: Craig Ringer <craig.ringer@2ndquadrant.com> Discussion: https://www.postgresql.org/message-id/flat/CAMsr+YF=+ctXBZj3ywmvKNUjWpxmuTuUKuv-rgbHGX5i5pLstQ@mail.gmail.com
1 parent 83e3239 commit 854434c

File tree

1 file changed

+25
-0
lines changed

1 file changed

+25
-0
lines changed

doc/src/sgml/regress.sgml

+25
Original file line numberDiff line numberDiff line change
@@ -351,6 +351,31 @@ make check LANG=C ENCODING=EUC_JP
351351
</para>
352352
</sect2>
353353

354+
<sect2>
355+
<title>Custom Server Settings</title>
356+
357+
<para>
358+
Custom server settings to use when running a regression test suite can be
359+
set in the <varname>PGOPTIONS</varname> environment variable (for settings
360+
that allow this):
361+
<screen>
362+
make check PGOPTIONS="-c log_checkpoints=on -c work_mem=50MB"
363+
</screen>
364+
When running against a temporary installation, custom settings can also be
365+
set by supplying a pre-written <filename>postgresql.conf</filename>:
366+
<screen>
367+
echo 'log_checkpoints = on' > test_postgresql.conf
368+
echo 'work_mem = 50MB' >> test_postgresql.conf
369+
make check EXTRA_REGRESS_OPTS="--temp-config=test_postgresql.conf"
370+
</screen>
371+
</para>
372+
373+
<para>
374+
This can be useful to enable additional logging, adjust resource limits,
375+
or enable extra run-time checks.
376+
</para>
377+
</sect2>
378+
354379
<sect2>
355380
<title>Extra Tests</title>
356381

0 commit comments

Comments
 (0)