Make new replication slot test code even less racy
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Mon, 19 Jul 2021 21:21:07 +0000 (17:21 -0400)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Mon, 19 Jul 2021 21:21:07 +0000 (17:21 -0400)
commitce413eba411633c5c5c9e326d6d0313c9764c711
tree209d4c7d469ab71e057abb50613d921945c22d90
parentbfa2a926daf812bbda2038aec073344693954f16
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.ntt@gmail.com>
Discussion: https://postgr.es/m/20210719.111318.2042379313472032754.horikyota.ntt@gmail.com
src/test/recovery/t/019_replslot_limit.pl