Re: control max length of parameter values logged
Alexey Bashtanov <bashtanov@imap.cc>
From: Alexey Bashtanov <bashtanov@imap.cc>
To: Tom Lane <tgl@sss.pgh.pa.us>, Justin Pryzby <pryzby@telsasoft.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, pgsql-hackers@postgresql.org
Date: 2020-04-02T00:29:04Z
Lists: pgsql-hackers
Attachments
- log_parameter_max_length_v4.patch (text/x-patch) patch v4
Hi, > The privilege argument seems irrelevant to me. We already decided > that the plan is (a) SUSET for non-error statement logging purposes and > (b) USERSET for logging caused by errors, and that would have to apply > to length limits as well as enable/disable ability. Otherwise a user > could pretty effectively disable logging by setting the length to 1. The only privilege that user can gain if we drop the boolean is to *enable* logging parameters on error. That gives user a little bit easier way to fill up the disk with logs, but they anyway can do that if they want to. If that's okay with everyone, please see the new version attached. Best, Alex
Commits
-
Improve user control over truncation of logged bind-parameter values.
- 0b34e7d307e6 13.0 landed