log_parameter_max_length_on_error

If greater than zero, each bind parameter value reported in error messages is trimmed to this many bytes. Zero (the default) disables including bind parameters in error messages. -1 allows bind parameters to be printed in full. If this value is specified without units, it is taken as bytes. Non-zero values of this setting add overhead, as PostgreSQL will need to store textual representations of parameter values in memory at the start of each statement, whether or not an error eventually occurs. The overhead is greater when bind parameters are sent in binary form than when they are sent as text, since the former case requires data conversion while the latter only requires copying the string.

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

13 14 15 16 17 18 19 20

boot val: 0
category: Reporting and Logging / What to Log
context: user
doc same as: Unknown
documented: true
enumvals: Unknown
extra desc: -1 means log values in full.
lang: en
max val: 1073741823
metadata version: 18
min val: -1
name: log_parameter_max_length_on_error
short desc: Sets the maximum length in bytes of data logged for bind parameter values when logging statements, on error.
source: pg-settings-source-snapshot
unit: B
vartype: integer

Definition PG 18

Non-zero values of this setting add overhead, as PostgreSQL will need to store textual representations of parameter values in memory at the start of each statement, whether or not an error eventually occurs. The overhead is greater when bind parameters are sent in binary form than when they are sent as text, since the former case requires data conversion while the latter only requires copying the string.

Compare versions

Complete source facts

doc html

<p>
        If greater than zero, each bind parameter value reported in error
        messages is trimmed to this many bytes.
        Zero (the default) disables including bind parameters in error
        messages.
        <code class="literal">-1</code> allows bind parameters to be printed in full.
        If this value is specified without units, it is taken as bytes.
       </p><p>
        Non-zero values of this setting add overhead, as
        <span class="productname">PostgreSQL</span> will need to store textual
        representations of parameter values in memory at the start of each
        statement, whether or not an error eventually occurs.  The overhead
        is greater when bind parameters are sent in binary form than when
        they are sent as text, since the former case requires data
        conversion while the latter only requires copying the string.
       </p>

documentation revision

{"inputs":[{"file":"runtime-config-logging.html","kind":"same-version-reviewed-manual","locale":"en","sha256":"278d913b9c0f735c5cd7b35fd7205826bbd9c449805370d2dbe54105c0ed1d88","version":"18.7"},{"file":"runtime-config-logging.html","kind":"same-version-reviewed-manual","locale":"zh-Hans","sha256":"68c010254e1859ec0b76f06a563babd51a6c38997f1242e35e4c6b649724b1cb","version":"18.7"}],"release":"18.7","runtime_remeasured":false,"source_revision":"pgdoc:b9f0e7232f60f380d642ac9b99226606c254b552"}

Source references

Original manual reference

Full definition and evidence JSON

Definition sources

center · PostgreSQL 18 · wiki-repair-20261023:371ae7aa482116c8dc245ac0baf12502111410a2edcfcdc9126ebb668b16cb0d

Text language: en · wiki-repair-20261023:371ae7aa482116c8dc245ac0baf12502111410a2edcfcdc9126ebb668b16cb0d