pgsql: Improve the stability of the recovery test 047_checkpoint_physic - Mailing list pgsql-committers

From Alexander Korotkov
Subject pgsql: Improve the stability of the recovery test 047_checkpoint_physic
Date
Msg-id E1ud6wO-0075WA-1z@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Improve the stability of the recovery test 047_checkpoint_physical_slot

Currently, the comments in 047_checkpoint_physical_slot. It shows an
incomplete intention to wait for checkpoint completion before performing
an immediate database stop.  However, an immediate node stop can occur both
before and after checkpoint completion.  Both cases should work correctly.
But we would like the test to be more stable and deterministic.  This is why
this commit makes this test explicitly wait for the checkpoint completion
log message.

Discussion: https://postgr.es/m/CAPpHfdurV-j_e0pb%3DUFENAy3tyzxfF%2ByHveNDNQk2gM82WBU5A%40mail.gmail.com
Discussion: https://postgr.es/m/aHXLep3OaX_vRTNQ%40paquier.xyz
Author: Alexander Korotkov <akorotkov@postgresql.org>
Reviewed-by: Michael Paquier <michael@paquier.xyz>
Backpatch-through: 17

Branch
------
master

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

Modified Files
--------------
src/test/recovery/t/047_checkpoint_physical_slot.pl | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)


pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: pgsql: Check status of nodes after regression test run in 027_stream_re
Next
From: Alexander Korotkov
Date:
Subject: pgsql: Fix infinite wait when reading a partially written WAL record