Re: log bind parameter values on error
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>, Alexey Bashtanov <bashtanov@imap.cc>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2019-12-10T21:12:47Z
Lists: pgsql-hackers
Attachments
Alexey: I would appreciate it if you give this patch a spin. Let me know if it does what you wanted it to do. On 2019-Dec-10, Alvaro Herrera wrote: > Here's a curious thing that happens with this patch. If you have > log_duration set so that parameters are logged during the bind phase, > and then an error occurs during the execution phase but you don't have > log_parameters_on_error set true, the second error will log the > parameters nonetheless ... because they were saved in the ParamListInfo > struct by the errdetail_params() call in the check_log_durations block > during bind. AFAICS this has a simple solution, which is to stop saving the parameter string in BuildParamLogString; instead, just *return* the string. Caller can then assign it into params->paramValuesStr if appropriate (which, in the case of errdetail_params(), it is not.) v22 does it like that. There is still a much smaller issue that if you have both log_durations set to log the params during bind, and log_parameters_on_error to true, the parameters will appear twice. But I think that's correct by definition. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Emit parameter values during query bind/execute errors
- ba79cb5dc841 13.0 landed
-
Add backend-only appendStringInfoStringQuoted
- 6cafde1bd43f 13.0 landed