Re: log bind parameter values on error
Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Alexey Bashtanov <bashtanov@imap.cc>
Cc: Andres Freund <andres@anarazel.de>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2019-03-14T12:38:53Z
Lists: pgsql-hackers
On 2019-02-15 15:02, Alexey Bashtanov wrote: > Hello Anders and Peter, > > Thanks for your messages. > Please see the new patch version attached. In my testing, I couldn't get this patch to do anything. Could you please share your testing steps? I did postgres -D data --log-parameters-on-error=on pgbench -i bench alter table pgbench_accounts alter column aid type smallint; pgbench -M extended -S -T 10 bench This will then error out on type overflows, but I don't see any parameters being logged: ERROR: value "62812" is out of range for type smallint STATEMENT: SELECT abalance FROM pgbench_accounts WHERE aid = $1; (In this case the error message contains the parameter value, so it's not a very practical case, but it should work, it seems.) Meanwhile, I have committed a patch that refactors the ParamListInfo initialization a bit, so you don't have to initialize hasTextValues in a bunch of places unrelated to your core code. So please rebase your patch on that. -- Peter Eisentraut http://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