Re: log bind parameter values on error
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
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-09T20:17:13Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes: > * Thoughts on changing the current usage of the ...Quoted() function in > postgres.c and pl_exec.c so that they print N characters (64) instead > of the current default of printing everything? I'm up for changing, > but have got no +1s on that. I think bloating log files with enormous > parameters is pointless. Meh ... people will inevitably complain that they needed to see the whole value, and we'll end up having to add another configuration variable. Let's not go there just yet. regards, tom lane
Commits
-
Emit parameter values during query bind/execute errors
- ba79cb5dc841 13.0 landed
-
Add backend-only appendStringInfoStringQuoted
- 6cafde1bd43f 13.0 landed