| Type: | integer |
| Default: | 80 (80MB) |
| Min: | 2 (2MB) |
| Max: | 2147483647 (2147483647MB) |
| Unit: | MB |
| Context: | sighup |
| Restart: | false |
| Since: | 9.5 |
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.
On StackOverflow
On pgsql-hackers
- Re: WIP: WAL prefetch (another approach)
- Enforce "max_wal_size/ min_wal_size must be at least twice wal_segment_size" limit while setting GUCs
- Re: Can postgres ever delete the recycled future WAL files to free-up disk space if max_wal_size is reduced or wal_recycle is set to off?
- RE: Hash index build performance tweak from sorting
- Re: [PATCH] Expose port->authn_id to extensions and triggers