Re: control max length of parameter values logged
| От | Tom Lane |
|---|---|
| Тема | Re: control max length of parameter values logged |
| Дата | |
| Msg-id | 27700.1583963788@sss.pgh.pa.us обсуждение |
| Ответ на | Re: control max length of parameter values logged (Alvaro Herrera <alvherre@2ndquadrant.com>) |
| Ответы |
Re: control max length of parameter values logged
|
| Список | pgsql-hackers |
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> Maybe it would make sense to always log complete parameters for error
> cases when that feature is enabled, and have the GUC only control the
> lengths logged for non-error cases?
I could get behind that. It's a bit different from the original
idea here, but I think it's closer to being real-world-useful.
Another way to slice this up would be to have a USERSET GUC that
controls truncation of parameter values in errors, and a separate
SUSET GUC that controls it for the non-error statement logging
cases. I'm not sure how much that's actually worth, but if we
feel that truncation in error cases can be useful, that's how
I'd vote to expose it.
regards, tom lane
В списке pgsql-hackers по дате отправления: