Date: Thu, 15 Jul 2021 12:09:45 -0400
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Marcin Krupowicz <marcin@071.ovh>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, jeff.janes@gmail.com,
	mk@071.ovh, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17103: WAL segments are not removed after exceeding
 max_slot_wal_keep_size
Message-ID: <202107151609.wx3mso7tpayc@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAK1NiawDV+d-u2yAi=t=PAqCO16RA16WVhe1QJiEk7DdQ1sEZQ@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/202107151609.wx3mso7tpayc%40alvherre.pgsql>
Precedence: bulk

On 2021-Jul-15, Marcin Krupowicz wrote:

> On Thu, 15 Jul 2021 at 08:33, Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote:
> > This is it. It is for the master branch but also applicable to 14 as
> > is. Not needed for earlier version.
> > I believe the test works for Windows but haven't checked.

Oh my, what an oversight.  Thanks Kyotaro for the investigation and fix;
I'll get it pushed today.

> Thanks for that. To clarify - is it not going to be fixed in 13.x?

It definitely is, since the feature is there.  I'll fix the apply
conflicts, since they're pretty trivial.  (No need to send a new patch.)

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"Ed is the standard text editor."
      http://groups.google.com/group/alt.religion.emacs/msg/8d94ddab6a9b0ad3