| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Petr Jelinek <petr(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PROPOSAL] Client Log Output Filtering |
| Date: | 2016-03-29 16:30:12 |
| Message-ID: | 56FAAD94.1080909@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/29/16 12:28 PM, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>> David Steele wrote:
>>> On 3/29/16 10:18 AM, Tom Lane wrote:
>>>> Repurposing COMMERROR is definitely starting to seem like a low-impact
>>>> solution compared to these others. Under what circumstances would you
>>>> be wanting hide-from-client with an elevel different from LOG, anyway?
>
>> So audit records would use COMMERROR? That sounds really bad to me.
>
> My proposal would be to invent a new elevel macro, maybe LOG_ONLY,
> for this purpose. But under the hood it'd be the same as COMMERROR.
My mistake, I see what you are getting at now.
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-03-29 16:33:19 | Re: [PROPOSAL] Client Log Output Filtering |
| Previous Message | Shulgin, Oleksandr | 2016-03-29 16:29:50 | Re: More stable query plans via more predictable column statistics |