On 02/07/14 22:10, Tom Lane wrote:
Greg Stark <st...@mit.edu> writes:
I think log_error_verbosity is a strange variable. It's useless for
expected user-facing errors but essential for unexpected errors that
indicate bugs in the code -- and you can only have it on for
everything or off for everything.
I'm finding I usually want it set to 'verbose' for anything that
PANICs or is generated by an elog() but it's just noise for anything
generated by an ereport() and is ERROR or below.
[...]
[ thinks for a bit... ] A slightly cleaner approach is to nominate
a specified set of SQLSTATEs, certainly including XX000 and perhaps
some others, as being ones that force verbose reporting. That would
have the same practical effect as far as elogs go, but wouldn't break
the nominal functional equivalence.
And that brings up the previous work on SQLSTATE-dependent choices
about whether to log at all. I remember a patch was submitted for
that but don't remember offhand why it didn't get committed. ISTM
we should think about reviving that and making the choice be not just
"log or not", but "no log, terse log, normal log, verbose log".
I had a patch for making log_min_error_statement configurable per
SQLSTATE in https://commitfest.postgresql.org/action/patch_view?id=1360
but you pointed out various issues in it and I didn't have time to
update it for 9.4. I'm going to rewrite it based on the comments and
submit it again for a 9.5 commitfest.
The same mechanism could be used to set verbosity per SQLSTATE.
/ Oskari
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
