Re: [PROPOSAL] Client Log Output Filtering - Mailing list pgsql-hackers

From David Steele
Subject Re: [PROPOSAL] Client Log Output Filtering
Date
Msg-id 56FAAA40.1070602@pgmasters.net
Whole thread Raw
In response to Re: [PROPOSAL] Client Log Output Filtering  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 3/29/16 11:37 AM, Alvaro Herrera wrote:
> 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?
>>
>> In pgaudit the log level for audit messages is user configurable but this
>> was mostly added for testing purposes on the client side.  I don't think it
>> would be a big deal to force the level to LOG when client output is
>> suppressed.
>
> So audit records would use COMMERROR?  That sounds really bad to me.

I'm not a big fan of it myself but my ideas don't seem to be getting any 
traction...

-- 
-David
david@pgmasters.net



pgsql-hackers by date:

Previous
From: Teodor Sigaev
Date:
Subject: Re: WIP: Access method extendability
Next
From: "Shulgin, Oleksandr"
Date:
Subject: Re: unexpected result from to_tsvector