Re: log bind parameter values on error
Greg Stark <stark@mit.edu>
From: Greg Stark <stark@mit.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
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-09T21:26:03Z
Lists: pgsql-hackers
On Mon, 9 Dec 2019 at 15:17, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > 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. I haven't been following this whole thread but my initial reaction is that this particular configuration parameter would actually carry it's weight. While some people have applications where they know the expected size of the data and can safely log the entire data to the logs other people deal with user-supplied data that can be very large. It would suck to have something like Gitlab dump entire merge diffs to the log and those aren't even very large, probably under a megabyte. Some users will have individual data that are up to 1GB.... -- greg
Commits
-
Emit parameter values during query bind/execute errors
- ba79cb5dc841 13.0 landed
-
Add backend-only appendStringInfoStringQuoted
- 6cafde1bd43f 13.0 landed