↑↓ select↵ open⌫ change scopeOpen full search

PG.CENTER connects PostgreSQL documentation, reference, and ecosystem knowledge. Maintained by Pigsty.

Wiki / Configuration Parameters

ignore_checksum_failure

Only has effect if data checksums are enabled. Detection of a checksum failure during a read normally causes PostgreSQL to report an error, aborting the current transaction. Setting ignore_checksum_failure to on causes the system to ignore the failure (but still report a warning), and continue processing. This behavior may cause crashes, propagate or hide corruption, or other serious problems. However, it may allow you to get past the error and retrieve undamaged tuples that might still be present in the table if the block header is still sane. If the header is corrupt an error will be reported even if this option is enabled. The default setting is off. 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

9.39.49.59.61011121314151617181920
boot val
off
category
Developer Options
context
superuser
doc same as
Unknown
documented
true
enumvals
Unknown
lang
en
max val
Unknown
metadata version
18
min val
Unknown
name
ignore_checksum_failure
short desc
Continues processing after a checksum failure.
source
pg-settings-source-snapshot
unit
Unknown
vartype
bool

Definition PG 18

Only has effect if data checksums are enabled.

Detection of a checksum failure during a read normally causes PostgreSQL to report an error, aborting the current transaction. Setting ignore_checksum_failure to on causes the system to ignore the failure (but still report a warning), and continue processing. This behavior may cause crashes, propagate or hide corruption, or other serious problems. However, it may allow you to get past the error and retrieve undamaged tuples that might still be present in the table if the block header is still sane. If the header is corrupt an error will be reported even if this option is enabled. The default setting is off. Only superusers and users with the appropriate SET privilege can change this setting.

Compare versions

Complete source facts

doc html

<p>
        Only has effect if <a class="link" href="/docs/18/checksums.html" title="28.2. Data Checksums">data checksums</a> are enabled.
       </p><p>
        Detection of a checksum failure during a read normally causes
        <span class="productname">PostgreSQL</span> to report an error, aborting the current
        transaction.  Setting <code class="varname">ignore_checksum_failure</code> to on causes
        the system to ignore the failure (but still report a warning), and
        continue processing.  This behavior may <span class="emphasis"><em>cause crashes, propagate
        or hide corruption, or other serious problems</em></span>.  However, it may allow
        you to get past the error and retrieve undamaged tuples that might still be
        present in the table if the block header is still sane. If the header is
        corrupt an error will be reported even if this option is enabled. The
        default setting is <code class="literal">off</code>.
        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"}

extra desc

Detection of a checksum failure normally causes PostgreSQL to report an error, aborting the current transaction. Setting ignore_checksum_failure to true causes the system to ignore the failure (but still report a warning), and continue processing. This behavior could cause crashes or other serious problems. Only has an effect if checksums are enabled.

Source references

Full definition and evidence JSON

Definition sources

center · PostgreSQL 18 · wiki-repair-20261023:e000ebc06c79b60fa759e0662b7245ff83ae4ca84ba7d70fd981bfedfc76398b

Text language: en · wiki-repair-20261023:e000ebc06c79b60fa759e0662b7245ff83ae4ca84ba7d70fd981bfedfc76398b