A.100. Release 4.0.24

Install system exit callback only after initialization of shared memory. (Muhammad Usama)

When the on-exit callback gets called because of a failure to acquire shared memory. The cleanup function can produce a segfault while accessing process_info, that lives in shared memory. Although we can also fix this by bailing out from the exit callback when process_info is NULL but installing the function after successful initialization of shared memory is a better approach as the rest of the system always assumes the process_info can never be NULL, and also, there is nothing to clean up before child processes are spawned.

Add schema qualification to some system catalog inquiry functions. (Tatsuo Ishii)

Fix find_primary_node_repeatedly doesn't terminate within search_primary_node_timeout. (Bo Peng)

Fix pgproto to work with bind message using params. (Tatsuo Ishii)

Previously pgproto can only process bind messages without params.

Clarify the meaning of stop mode. (Tatsuo Ishii)

Enhance online recovery documentation. (Bo Peng)

Mention that 2nd stage of online recovery does not work properly only for multiple pgpool nodes without watchdog enabled.

Fix occasional 069.memory_leak_extended test failure. (Tatsuo Ishii)

It turned out that reason of the occasional test failure is, pgpool child process is gone before running ps command after pgbench finishes. The cause is a kind mismatch FATAL error, "DISCARD ALL cannot be executed within a pipeline". To fix this, run pgbench in background and get the process size before pgbench finishes.

Discussion: https://www.pgpool.net/pipermail/pgpool-hackers/2023-May/004338.html