Wiki / Configuration Parameters
wal_consistency_checking
This parameter is intended to be used to check for bugs in the WAL redo routines. When enabled, full-page images of any buffers modified in conjunction with the WAL record are added to the record. If the record is subsequently replayed, the system will first apply each record and then test whether the buffers modified by the record match the stored images. In certain cases (such as hint bits), minor variations are acceptable, and will be ignored. Any unexpected differences will result in a fatal error, terminating recovery. The default value of this setting is the empty string, which disables the feature. It can be set to all to check all records, or to a comma-separated list of resource managers to check only records originating from those resource managers. Currently, the supported resource managers are heap, heap2, btree, hash, gin, gist, sequence, spgist, brin, and generic. Extensions may define additional resource managers. Only superusers and users with the appropriate SET privilege can change this setting.
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
- Unknown
- category
- Developer Options
- context
- superuser
- doc same as
- Unknown
- documented
- true
- enumvals
- Unknown
- extra desc
- Full-page images will be logged for all data blocks and cross-checked against the results of WAL replay.
- lang
- en
- max val
- Unknown
- metadata version
- 18
- min val
- Unknown
- name
- wal_consistency_checking
- short desc
- Sets the WAL resource managers for which WAL consistency checks are done.
- source
- pg-settings-source-snapshot
- unit
- Unknown
- vartype
- string
Definition PG 18
This parameter is intended to be used to check for bugs in the WAL redo routines. When enabled, full-page images of any buffers modified in conjunction with the WAL record are added to the record. If the record is subsequently replayed, the system will first apply each record and then test whether the buffers modified by the record match the stored images. In certain cases (such as hint bits), minor variations are acceptable, and will be ignored. Any unexpected differences will result in a fatal error, terminating recovery.
The default value of this setting is the empty string, which disables
the feature. It can be set to all to check all
records, or to a comma-separated list of resource managers to check
only records originating from those resource managers. Currently,
the supported resource managers are heap,
heap2, btree, hash,
gin, gist, sequence,
spgist, brin, and generic.
Extensions may define additional resource managers. Only superusers and users with
the appropriate SET privilege can change this setting.
Compare versions
Complete source facts
doc html
<p>
This parameter is intended to be used to check for bugs in the WAL
redo routines. When enabled, full-page images of any buffers modified
in conjunction with the WAL record are added to the record.
If the record is subsequently replayed, the system will first apply
each record and then test whether the buffers modified by the record
match the stored images. In certain cases (such as hint bits), minor
variations are acceptable, and will be ignored. Any unexpected
differences will result in a fatal error, terminating recovery.
</p><p>
The default value of this setting is the empty string, which disables
the feature. It can be set to <code class="literal">all</code> to check all
records, or to a comma-separated list of resource managers to check
only records originating from those resource managers. Currently,
the supported resource managers are <code class="literal">heap</code>,
<code class="literal">heap2</code>, <code class="literal">btree</code>, <code class="literal">hash</code>,
<code class="literal">gin</code>, <code class="literal">gist</code>, <code class="literal">sequence</code>,
<code class="literal">spgist</code>, <code class="literal">brin</code>, and <code class="literal">generic</code>.
Extensions may define additional resource managers. Only superusers and users with
the appropriate <code class="literal">SET</code> privilege can change this setting.
</p>documentation revision
{"inputs":[{"file":"runtime-config-developer.html","kind":"same-version-reviewed-manual","locale":"en","sha256":"a3f6a107ed6ba4edaf6df03e52f4a469bd09350d545e4ff419e62844025ec1cf","version":"18.7"},{"file":"runtime-config-developer.html","kind":"same-version-reviewed-manual","locale":"zh-Hans","sha256":"e7e22aa5738a1d376b84af1adca796c5e14746266733f925eb50c3ef86a50655","version":"18.7"}],"release":"18.7","runtime_remeasured":false,"source_revision":"pgdoc:b9f0e7232f60f380d642ac9b99226606c254b552"}Source references
Full definition and evidence JSON
Definition sources
center · PostgreSQL 18 · wiki-repair-20261023:c73bc17211d122b9b41569d0130d3150514bed92937c59b6de47259ec92efff9
Text language: en · wiki-repair-20261023:c73bc17211d122b9b41569d0130d3150514bed92937c59b6de47259ec92efff9