pgpool-II 4.7.0 Documentation
Prev | Up | Appendix A. Release Notes | Next

# A.17. Release 4.5.1

> Release Date: 2024-02-29

## A.17.1. Changes

- Remove restore_command from sample scripts. (Bo Peng)

  Restore_command is not required because replication slot is enabled. It causes occasional failover failure.

## A.17.2. Bug fixes

- Fixed the default values of recovery_user, failover_on_backend_shutdown and insert_lock. (Bo Peng)

  Because the default value of `recovery_user` should be same as health_check_user and sr_check_user, I changed the default value from '' to 'nobody'.

  The correct default value of `failover_on_backend_shutdown` should be "false" and the correct default value of `insert_lock` should be "on".

- Fixed statement_level_load_balance with BEGIN etc. (Tatsuo Ishii)

  When `statement_level_load_balance` is enabled, BEGIN/END/COMMIT/ABORT/SET/SAVEPOINT/RELEASE SAVEPOINT/DEALLOCATE ALL/DISCARD were sent to primary node and all standby nodes even if load_balance_mode is off. This is not only plain wrong but caused slow down if one of the standby nodes are in remote network.

  Fix this in that pgpool sends such queries to primary node only when `load_balance_mode` is off.

  Reported: https://www.pgpool.net/pipermail/pgpool-general/2024-January/009059.html

  Discussion: https://www.pgpool.net/pipermail/pgpool-hackers/2024-February/004423.html

## A.17.3. Documents

- Fix Japanese watchdog document. (Tatsuo Ishii)

  It mistakenly used "master" watchdog node instead of "leader".

- Fix English watchdog document. (Tatsuo Ishii)

  It mistakenly used "main" PostgreSQL node instead of "primary".

- Fix Japanese delay_threshold_by_time document mistake. (Bo Peng)

  If this value is specified without units, it should be taken as milliseconds.

## A.17.4. Regression Tests

- Enhance 037.failover_session/test.sh. (Tatsuo Ishii)

  Previously it mistakenly executed `pg_ctl stop` after starting pgbench in background. The smart shutdown always allows pgbench to run successfully with pgbench -C option not being set because backend does not shutdown while client session continues.

  In order to shutdown backend in the middle of pgbench run, tweak health check parameters so that it detects the backend down as soon as possible. This will trigger failover in the middle of pgbench run.

Prev | Home | Next
Release 4.5.2 | Up | Release 4.5.0