Re: max_slot_wal_keep_size and wal_keep_segments - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: max_slot_wal_keep_size and wal_keep_segments
Date
Msg-id 20200701032605.GA16707@alvherre.pgsql
Whole thread Raw
In response to max_slot_wal_keep_size and wal_keep_segments  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: max_slot_wal_keep_size and wal_keep_segments  (Fujii Masao <masao.fujii@oss.nttdata.com>)
List pgsql-hackers
On 2020-Jun-30, Fujii Masao wrote:

> Hi,
> 
> When I talked about max_slot_wal_keep_size as new feature in v13
> at the conference, I received the question like "Why are the units of
> setting values in max_slot_wal_keep_size and wal_keep_segments different?"
> from audience. That difference looks confusing for users and
> IMO it's better to use the same unit for them. Thought?

Do we still need wal_keep_segments for anything?  Maybe we should
consider removing that functionality instead ... and even if we don't
remove it in 13, then what is the point of renaming it only to remove it
shortly after?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: HashAgg's batching counter starts at 0, but Hash's starts at 1.
Next
From: Alvaro Herrera
Date:
Subject: Re: Intermittent BRIN failures on hyrax and lousyjack