Horton

Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size

Alvaro Herrera <alvherre@alvh.no-ip.org>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: tgl@sss.pgh.pa.us, jeff.janes@gmail.com, mk@071.ovh, pgsql-bugs@lists.postgresql.org
Date: 2021-08-02T13:08:35Z
Lists: pgsql-bugs 
On 2021-Aug-02, Kyotaro Horiguchi wrote:

> Agreed. I hope this is the last failure..

There have been no failures since:

https://buildfarm.postgresql.org/cgi-bin/show_failures.pl?max_days=20&branch=HEAD&branch=REL_14_STABLE&branch=REL_13_STABLE&member=&stage=recoveryCheck&filter=Submit

-- 
Álvaro Herrera           39°49'30"S 73°17'W  —  https://www.EnterpriseDB.com/
"El hombre nunca sabe de lo que es capaz hasta que lo intenta" (C. Dickens)

Commits

  1. Close yet another race condition in replication slot test code

  2. Make new replication slot test code even less racy

  3. Make new replication slot test code less racy

  4. Advance old-segment horizon properly after slot invalidation