Clarify log_parameter_max_length docs regarding log_min_duration_statement vs log_duration

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Clarify log_parameter_max_length docs regarding log_min_duration_statement vs log_duration
Date: 2026-04-10 03:00:38
Message-ID: CAHGQGwGnCVMVz8-LU9F8Sh57bkQX3jMZzx7age7M0LFEz5=Fog@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Hi,

While reviewing the log_statement_max_length patch [1], I noticed the docs
for log_parameter_max_length say:

This setting only affects log messages printed as a result of
log_statement, log_duration, and related settings.”

However, enabling only log_duration does not log bind parameter values,
so in practice log_parameter_max_length does not seem to affect messages
generated by log_duration. Bind parameters are logged, for example, when
log_min_duration_statement is set.

Given that, referencing log_duration here seems misleading. Would it be
better to mention log_min_duration_statement instead?

I've attached a patch that makes this change.

Regards,

[1] https://postgr.es/m/CA+E0NR4S+NC6+QHyY_vUuQZMzLhKqczMx-jJVqtjAxF6+=JwAA@mail.gmail.com

--
Fujii Masao

Attachment Content-Type Size
v1-0001-doc-Fix-log_parameter_max_length-docs-to-referenc.patch application/octet-stream 1.6 KB

Browse pgsql-docs by date

  From Date Subject
Next Message Fujii Masao 2026-04-10 15:34:18 Re: pgsql: ssl: Serverside SNI support for libpq
Previous Message Shinya Kato 2026-04-08 01:49:24 Re: doc: Clarify ANALYZE VERBOSE output