[pgpool-committers: 8298] pgpool: Allow to run regression test against existing installation with

[Tatsuo Ishii]

Allow to run regression test against existing installation without recompiling.

It is possible to run regression test using existing installation.

regression.sh -m noinstall

However some of tests fail in this case because those tests require
pgpool to be compiled with variable HEALTHCHECK_DEBUG is set. This is
only possible in following procedure.

make clean
cd src/test/regression
./regress.sh

To run the regression test against existing installation new config
variable "health_check_test" is added. The source code is always
compiled as if HEALTHCHECK_DEBUG is set. The test facility is not
activated unless health_check_test is set to on.

For now I push to only master branch. After some tests, I am going to
push to all supported branches. I know adding new parameter to stable
branches is unusual but the feature is for enhancing test and it is
not visible to ordinal users. So I think my plan is justified by them.

Discussion: https://www.pgpool.net/pipermail/pgpool-hackers/2021-December/004078.html

Branch
------
V4_2_STABLE

Details
-------
https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=8df03d269d5be1b6e3c3e788e28b5c89640f2b95

Modified Files
--------------
doc.ja/src/sgml/misc-config.sgml      | 75 +++++++++++++++++++++++++++++++++++
doc.ja/src/sgml/ref/pgpool_setup.sgml | 27 +++++++++++++
doc/src/sgml/misc-config.sgml         | 47 ++++++++++++++++++++++
doc/src/sgml/ref/pgpool_setup.sgml    | 21 ++++++++++
src/Makefile.am                       |  3 +-
src/config/pool_config_variables.c    | 10 +++++
src/include/pool_config.h             |  1 +
src/main/health_check.c               | 52 ++++++------------------
src/test/pgpool_setup.in              |  8 ++++
src/test/regression/regress.sh        |  4 +-
10 files changed, 205 insertions(+), 43 deletions(-)