Wiki / Configuration Parameters
wal_skip_threshold
When wal_level is minimal and a transaction commits after creating or rewriting a permanent relation, this setting determines how to persist the new data. If the data is smaller than this setting, write it to the WAL log; otherwise, use an fsync of affected files. Depending on the properties of your storage, raising or lowering this value might help if such commits are slowing concurrent transactions. If this value is specified without units, it is taken as kilobytes. The default is two megabytes (2MB).
English manual coverage begins with PostgreSQL 7.4. Source history and runtime observations have their own recorded version boundaries.
Reading PG 18·Select a recorded version
- boot val
- 2048
- category
- Write-Ahead Log / Settings
- context
- user
- documented
- true
- enumvals
- Unknown
- extra desc
- Unknown
- lang
- en
- max val
- 2147483647
- metadata version
- 18
- min val
- 0
- name
- wal_skip_threshold
- short desc
- Minimum size of new file to fsync instead of writing WAL.
- source
- pg-settings-source-snapshot
- unit
- kB
- vartype
- integer
Definition PG 18
When wal_level is minimal and a transaction commits after creating or rewriting a permanent relation, this setting determines how to persist the new data. If the data is smaller than this setting, write it to the WAL log; otherwise, use an fsync of affected files. Depending on the properties of your storage, raising or lowering this value might help if such commits are slowing concurrent transactions. If this value is specified without units, it is taken as kilobytes. The default is two megabytes (2MB).
Compare versions
Source references
Full definition and evidence JSON
Definition sources
center · PostgreSQL 18 · wiki-repair-20261023:0c8be50578426e00efdb6b9c9acd5d9e2786541939c62cb23fa76ba9794c9fc5
Text language: en · wiki-repair-20261023:0c8be50578426e00efdb6b9c9acd5d9e2786541939c62cb23fa76ba9794c9fc5