Re: log_error_verbosity and unexpected errors - Mailing list pgsql-hackers

From Tom Lane
Subject Re: log_error_verbosity and unexpected errors
Date
Msg-id 20729.1404330312@sss.pgh.pa.us
Whole thread Raw
In response to Re: log_error_verbosity and unexpected errors  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
Merlin Moncure <mmoncure@gmail.com> 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
would be equally useful.  That would also lend some support to my gut
feeling that it should not be elog-vs-ereport that drives the decision,
because the client is not going to be able to tell which was used.
But the client side could have functionally equivalent behavior if it were
based on SQLSTATE and/or severity level.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: Aggregate function API versus grouping sets
Next
From: Kevin Grittner
Date:
Subject: Re: Patch to send transaction commit/rollback stats to the stats collector unconditionally.