On 02/07/14 22:10, Tom Lane wrote:
Greg Stark 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 fi
Merlin Moncure writes:
> Not trying to hijack your thread, just wondering out load if a
> SQLSTATE driven verbosity decision, if you were to do that,
> could/should also be hooked to client console logging and/or psql.
Yeah, you could certainly argue that a similar facility on the client side
wou
On Wed, Jul 2, 2014 at 2:10 PM, Tom Lane wrote:
> Greg Stark 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
Greg Stark 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
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
P
