database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2026-10-23 13:29:09 +03:00
Code Activity

doc: Fix log_parameter_max_length docs to reference log_min_duration_statement

Browse Source 
The documentation for log_parameter_max_length said it affects messages
generated by log_duration. However, log_duration alone does not log bind
parameter values, so this is misleading.

This commit updates the documentation to reference log_min_duration_statement,
which can log bind parameters, to better reflect actual behavior.

Backpatch to all supported versions.

Author: Fujii Masao <masao.fujii@gmail.com>
Reviewed-by: Surya Poondla <suryapoondla4@gmail.com>
Discussion: https://postgr.es/m/CAHGQGwGnCVMVz8-LU9F8Sh57bkQX3jMZzx7age7M0LFEz5=Fog@mail.gmail.com
Backpatch-through: 14
This commit is contained in:
Fujii Masao
2026-07-16 13:35:36 +09:00
parent 9171f77db2
commit 54bf009052
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
doc/src/sgml/config.sgml
View File

@@ -8427,9 +8427,10 @@ log_line_prefix = '%m [%p] %q%u@%d/%a '
<para>
This setting only affects log messages printed as a result of
<xref linkend="guc-log-statement"/>,
<xref linkend="guc-log-duration"/>, and related settings. Non-zero
values of this setting add some overhead, particularly if parameters
are sent in binary form, since then conversion to text is required.
<xref linkend="guc-log-min-duration-statement"/>, and related settings.
Non-zero values of this setting add some overhead, particularly
if parameters are sent in binary form, since then conversion to
text is required.
</para>
</listitem>
</varlistentry>