Tweak TAP test for worker terminations in worker_spi The test has been reported as having a race condition for the case of a worker that should be terminated after a database rename. Based on the report received from buildfarm member jay, the database renamed is accessed by a different session, preventing the ALTER DATABASE to complete, ultimately failing the test.
Honestly, I am not completely sure what is the origin of this disturbance, but two possibilities are an autovacuum or parallel worker (due to debug_parallel_query being used by the host). In order to (hopefully) stabilize the test, autovacuum and debug_parallel_query are now disabled in the configuration of the node used in the test. The failure is hard to reproduce, so it will take a few weeks to make sure that the test has become stable. Let's see where it goes. Reported-by: Aya Iwata <[email protected]> Discussion: https://postgr.es/m/os3pr01mb8889505e2f3e443cca4bd72eea...@os3pr01mb8889.jpnprd01.prod.outlook.com Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/af8837a10bc70d5e815a1bda986429a2a73ad174 Modified Files -------------- src/test/modules/worker_spi/t/002_worker_terminate.pl | 5 +++++ 1 file changed, 5 insertions(+)
