| From: | Alexey Bashtanov <bashtanov(at)imap(dot)cc> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: control max length of parameter values logged |
| Date: | 2020-04-02 00:29:04 |
| Message-ID: | f63e1977-5773-3d71-3439-3b65d12cdb8e@imap.cc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| Attachment | Content-Type | Size |
|---|---|---|
| log_parameter_max_length_v4.patch | text/x-patch | 14.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2020-04-02 00:29:56 | Re: proposal \gcsv |
| Previous Message | Peter Geoghegan | 2020-04-02 00:26:04 | Re: snapshot too old issues, first around wraparound and then more. |