From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: max_slot_wal_keep_size and wal_keep_segments
Date: Wed, 1 Jul 2020 21:50:56 +0900
Message-ID: <ad678ce4-199f-0bd9-7aff-6ef8501dd36e@oss.nttdata.com> (raw)
In-Reply-To: <20200701032605.GA16707@alvherre.pgsql>
References: <20200701032605.GA16707@alvherre.pgsql>
On 2020/07/01 12:26, Alvaro Herrera wrote:
> 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?
Yeah, personally I like wal_keep_segments because its setting is very
simple and no extra operations on replication slots are necessary.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: masao.fujii@oss.nttdata.com, alvherre@2ndquadrant.com
Subject: Re: max_slot_wal_keep_size and wal_keep_segments
In-Reply-To: <ad678ce4-199f-0bd9-7aff-6ef8501dd36e@oss.nttdata.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox