postgresql

mirror of https://github.com/postgres/postgres.git synced 2026-03-11 10:45:17 -04:00

History

Peter Eisentraut 8e93a516e6 Don't propagate PGAPPNAME through pg_ctl in tests When libpq is loaded in the server (for instance, by libpqwalreceiver), it may use libpq environment variables set in the postmaster environment for connection parameter defaults. This has some confusing effects in our test suites. For example, the TAP test infrastructure sets PGAPPNAME to allow identifying clients in the server log. But this environment variable is also inherited by temporary servers started with pg_ctl and is then in turn used by libpqwalreceiver as the application_name for connecting to remote servers where it then shows up in pg_stat_replication and is relevant for things like synchronous_standby_names. Replication already has a suitable default for application_name, and overriding that accidentally then requires the individual test cases to re-override that, which is all very confusing and unnecessary. To fix, unset PGAPPNAME temporarily before running pg_ctl start or restart in the tests. More comprehensive approaches like unsetting all environment variables in pg_ctl were considered but might be too complicated to achieve portably. The now unnecessary re-overriding of application_name by test cases is also removed. Reviewed-by: Noah Misch <noah@leadboat.com> Discussion: https://www.postgresql.org/message-id/flat/33383613-690e-6f1b-d5ba-4957ff40f6ce@2ndquadrant.com		2019-03-16 08:58:40 +01:00
..
t	Don't propagate PGAPPNAME through pg_ctl in tests	2019-03-16 08:58:40 +01:00
.gitignore	Minor tweaks for new src/test/recovery	2016-02-29 18:16:59 -03:00
Makefile	Add TAP test to check consistency of minimum recovery LSN	2019-03-13 14:58:24 +09:00
README	Fix bogus loop logic in 013_crash_restart test's pump_until subroutine.	2018-08-12 18:05:49 -04:00

README

src/test/recovery/README

Regression tests for recovery and replication
=============================================

This directory contains a test suite for recovery and replication.

Running the tests
=================

NOTE: You must have given the --enable-tap-tests argument to configure.
Also, to use "make installcheck", you must have built and installed
contrib/test_decoding in addition to the core code.

Run
    make check
or
    make installcheck
You can use "make installcheck" if you previously did "make install".
In that case, the code in the installation tree is tested.  With
"make check", a temporary installation tree is built from the current
sources and then tested.

Either way, this test initializes, starts, and stops several test Postgres
clusters.