postgresql

History

Amit Kapila d13ff82319 Fix BF failure in commit `93db6cbda0`. The code to match the required LOG in the test was not robust enough to match it. It was using a very specific format to search the required message which doesn't work when one uses log_error_verbosity = verbose. Author: Hou Zhijie Discussion: https://postgr.es/m/CAA4eK1KcQSk7wzC7Zfrth9OhrjW2HvxL4tKgU42qqH7p6jn+FA@mail.gmail.com		2024-02-22 18:26:40 +05:30
..
t	Fix BF failure in commit `93db6cbda0`.	2024-02-22 18:26:40 +05:30
.gitignore	Minor tweaks for new src/test/recovery	2016-02-29 18:16:59 -03:00
Makefile	Update copyright for 2024	2024-01-03 20:49:05 -05:00
README	Force testing of query jumbling in 027_stream_regress.pl	2023-03-03 10:41:51 +09:00
meson.build	Add a failover option to subscriptions.	2024-01-30 16:49:28 +05:30

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/pg_prewarm, contrib/pg_stat_statements and 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.

If you want to test WAL consistency checking, add
PG_TEST_EXTRA=wal_consistency_checking
to the "make" command.  This is resource-intensive, so it's not done
by default.

See src/test/perl/README for more info about running these tests.