| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: max_slot_wal_keep_size and wal_keep_segments |
| Date: | 2020-07-01 12:50:56 |
| Message-ID: | ad678ce4-199f-0bd9-7aff-6ef8501dd36e@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amul Sul | 2020-07-01 12:52:25 | Re: Cleanup - adjust the code crossing 80-column window limit |
| Previous Message | Daniel Gustafsson | 2020-07-01 12:50:14 | Re: WIP: expression evaluation improvements |