As long as WAL disk usage stays below this setting, old WAL files are always recycled for future use at a checkpoint, rather than removed. This can be used to ensure that enough WAL space is reserved to handle spikes in WAL usage, for example when running large batch jobs. If this value is specified without units, it is taken as megabytes. The default is 80 MB. This parameter can only be set in the postgresql.conf file or on the server command line.
- Re: checkpointer: PANIC: could not fsync file: No such file or directory
- Re: [HACKERS] Restricting maximum keep segments by repslots
- Re: min_wal_size > max_wal_size is accepted
- Fwd: bad wal on replica / incorrect resource manager data checksum in record / zfs
- Re: Connections dropping while using Postgres backend DB with Ejabberd