Make new replication slot test code even less racy
Alvaro Herrera <alvherre@alvh.no-ip.org>
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
Files
| Path | Change | +/− |
|---|---|---|
| src/test/recovery/t/019_replslot_limit.pl | modified | +14 −1 |
Discussion
- BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size 27 messages · 2021-07-13 → 2021-08-02