Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
Date
Msg-id 202107152049.3kftantyynji@alvherre.pgsql
Whole thread Raw
In response to Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-bugs
On 2021-Jul-15, Kyotaro Horiguchi wrote:

> > Thanks! I saw the issue here.  Some investigation showd me a doubious
> > motion of XLogCtl->repliationSlotMinLSN.  Slot invalidation is
> > forgetting to recalculate it and that misbehavior retreats the segment
> > horizon.

Actually, looking again, isn't this supposed to happen in KeepLogSeg()?
We have a block that caps to max_slot_wal_keep_size_mb there ... why did
that not work?

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"Sallah, I said NO camels! That's FIVE camels; can't you count?"
(Indiana Jones)



pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size