pgsql: Make new replication slot test code even less racy

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Make new replication slot test code even less racy
Date: 2021-07-19 21:21:50
Message-ID: [email protected]
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Make new replication slot test code even less racy

Further fix the test code in ead9e51e8236, this time by waiting until
the checkpoint has completed before moving on; this ensures that the
WAL segment removal has already happened when we create the next slot.

Author: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Discussion: https://postgr.es/m/[email protected]

Branch
------
REL_14_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/1e8751380836056fdf546433dcf0328bc18c9313

Modified Files
--------------
src/test/recovery/t/019_replslot_limit.pl | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2021-07-19 23:20:49 pgsql: Don't use #if inside function-like macro arguments.
Previous Message Peter Eisentraut 2021-07-19 07:54:31 pgsql: Make UCS_to_most.pl process encodings in sorted order