| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: log_error_verbosity and unexpected errors |
| Date: | 2014-07-02 19:45:12 |
| Message-ID: | 20729.1404330312@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Merlin Moncure <mmoncure(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2014-07-02 19:49:27 | Re: Patch to send transaction commit/rollback stats to the stats collector unconditionally. |
| Previous Message | Andrew Gierth | 2014-07-02 19:44:55 | Re: Aggregate function API versus grouping sets |