log_error_verbosity and unexpected errors

From: Greg Stark <stark(at)mit(dot)edu>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: log_error_verbosity and unexpected errors
Date: 2014-07-02 18:45:29
Message-ID: CAM-w4HMStzNspuA9nJBij1ADKeJ0grbUutJsPVRY4ao8wSSMAw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

The minimum suggested change would to make it implicitly true for
PANIC and any unexpected elog()s and leave the GUC for enabling it in
the other cases.

--
greg

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-07-02 18:47:04 Re: Aggregate function API versus grouping sets
Previous Message Sawada Masahiko 2014-07-02 18:31:09 Re: TODO : Allow parallel cores to be used by vacuumdb [ WIP ]