Re: Logging query parmeters in auto_explain
Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
From: Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2022-06-07T11:18:52Z
Lists: pgsql-hackers
Attachments
- v2-0001-Log-query-parameters-in-auto_explain.patch (text/x-diff)
Michael Paquier <michael@paquier.xyz> writes:
> On Tue, May 31, 2022 at 09:33:20PM +0100, Dagfinn Ilmari Mannsåker wrote:
>> Here's a patch that adds a corresponding
>> auto_explain.log_parameter_max_length config setting, which controls the
>> "Query Parameters" node in the logged plan. Just like in core, the
>> default is -1, which logs the parameters in full, and 0 disables
>> parameter logging, while any other value truncates each parameter to
>> that many bytes.
>
> With a behavior similar to the in-core log_parameter_max_length, this
> looks rather sane to me. This is consistent with the assumptions of
> errdetail_params().
That was the intention, yes.
> +$node->append_conf('postgresql.conf', "auto_explain.log_parameter_max_length = -1");
> Nit. You don't need this change in the TAP test, as this is the
> default value to log everything.
Point, fixed in the attached v2. I've also added a test that truncation
and disabling works.
- ilmari
Commits
-
autho_explain: Add GUC to log query parameters
- d4bfe4128170 16.0 landed
-
Refactor the TAP test of auto_explain
- 550bc0a6c0c6 16.0 landed