Re: max_slot_wal_keep_size comment in postgresql.conf
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: jeff.janes@gmail.com, pgsql-hackers@postgresql.org
Date: 2020-05-27T06:11:00Z
Lists: pgsql-hackers
On Wed, May 27, 2020 at 10:46:27AM +0900, Kyotaro Horiguchi wrote: > Agreed. It should be a leftover at the time the unit was changed > (before committed) to MB from bytes. The default value makes the > confusion worse. > > Is the following works? > > #max_slot_wal_keep_size = -1 # in MB; -1 disables Indeed, better to fix that. The few GUCs using memory units that have such a mention in their comments use the actual name of the memory unit, and not its abbreviation (see log_temp_files). So it seems more logic to me to just use "in megabytes; -1 disables", that would be also more consistent with the time-unit-based ones. -- Michael
Commits
-
Fix some mentions to memory units in postgresql.conf.sample
- 55ca50deb8ff 13.0 landed