pgsql: Fix the random test failure in 001_rep_changes. - Mailing list pgsql-committers

From Amit Kapila
Subject pgsql: Fix the random test failure in 001_rep_changes.
Date
Msg-id E1mLILV-0000G8-0o@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix the random test failure in 001_rep_changes.

The check to test whether the subscription workers were restarting after a
change in the subscription was failing. The reason was that the test was
assuming the walsender started before it reaches the 'streaming' state and
the walsender was exiting due to an error before that. Now, the walsender
was erroring out before reaching the 'streaming' state because it tries to
acquire the slot before the previous walsender has exited.

In passing, improve the die messages so that it is easier to investigate
the failures in the future if any.

Reported-by: Michael Paquier, as per buildfarm
Author: Ajin Cherian
Reviewed-by: Masahiko Sawada, Amit Kapila
Backpatch-through: 10, where this test was introduced
Discussion: https://postgr.es/m/YRnhFxa9bo73wfpV@paquier.xyz

Branch
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/b51985d8a0e1a7487d17559cbeefc87892c4d916

Modified Files
--------------
src/test/subscription/t/001_rep_changes.pl | 26 ++++++++++++++------------
1 file changed, 14 insertions(+), 12 deletions(-)


pgsql-committers by date:

Previous
From: Peter Geoghegan
Date:
Subject: pgsql: VACUUM VERBOSE: Don't report "pages removed".
Next
From: Fujii Masao
Date:
Subject: pgsql: pgbench: Fix bug in measurement of disconnection delays.