Re: max_slot_wal_keep_size and wal_keep_segments
David Steele <david@pgmasters.net>
From: David Steele <david@pgmasters.net>
To: Fujii Masao <masao.fujii@oss.nttdata.com>,
Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: alvherre@2ndquadrant.com, pgsql-hackers@postgresql.org
Date: 2020-07-20T12:21:46Z
Lists: pgsql-hackers
On 7/20/20 6:02 AM, Fujii Masao wrote: > > > On 2020/07/20 13:48, Fujii Masao wrote: >> >> >> On 2020/07/17 20:24, David Steele wrote: >>> >>> On 7/17/20 5:11 AM, Fujii Masao wrote: >>>> >>>> >>>> On 2020/07/14 20:30, David Steele wrote: >>>>> On 7/14/20 12:00 AM, Fujii Masao wrote: >>>>>> >>>>>> The patch was no longer applied cleanly because of recent commit. >>>>>> So I updated the patch. Attached. >>>>>> >>>>>> Barring any objection, I will commit this patch. >>>>> >>>>> This doesn't look right: >>>>> >>>>> + the <xref linkend="guc-wal-keep-size"/> most recent megabytes >>>>> + WAL files plus one WAL file are >>>>> >>>>> How about: >>>>> >>>>> + <xref linkend="guc-wal-keep-size"/> megabytes of >>>>> + WAL files plus one WAL file are >>>> >>>> Thanks for the comment! Isn't it better to keep "most recent" part? >>>> If so, what about either of the followings? >>>> >>>> 1. <xref linkend="guc-wal-keep-size"/> megabytes of WAL files plus >>>> one WAL file that were most recently generated are kept all time. >>>> >>>> 2. <xref linkend="guc-wal-keep-size"/> megabytes + <xref >>>> linkend="guc-wal-segment-size"> bytes >>>> of WAL files that were most recently generated are kept all time. >>> >>> "most recent" seemed implied to me, but I see your point. >>> >>> How about: >>> >>> + the most recent <xref linkend="guc-wal-keep-size"/> megabytes of >>> + WAL files plus one additional WAL file are >> >> I adopted this and pushed the patch. Thanks! >> >> Also we need to update the release note for v13. What about adding the >> following? >> >> ------------------------------------ >> Rename configuration parameter wal_keep_segments to wal_keep_size. >> >> This allows how much WAL files to retain for the standby server, by >> bytes instead of the number of files. >> If you previously used wal_keep_segments, the following formula will >> give you an approximately equivalent setting: >> >> wal_keep_size = wal_keep_segments * wal_segment_size (typically 16MB) >> ------------------------------------ I would rework that first sentence a bit. How about: + This determines how much WAL to retain for the standby server, + specified in megabytes rather than number of files. The rest looks fine to me. Regards, -- -David david@pgmasters.net
Commits
-
doc: Mention the rename of wal_keep_segments GUC in release note.
- 128fd0a65ae5 13.0 landed
-
Rename wal_keep_segments to wal_keep_size.
- f5dff45962ec 13.0 landed
- c3fe108c025e 14.0 landed