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

From Tom Lane
Subject Re: [PROPOSAL] Client Log Output Filtering
Date
Msg-id 14531.1459268920@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PROPOSAL] Client Log Output Filtering  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [PROPOSAL] Client Log Output Filtering
Re: [PROPOSAL] Client Log Output Filtering
List pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.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.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: WIP: Access method extendability
Next
From: "Shulgin, Oleksandr"
Date:
Subject: Re: More stable query plans via more predictable column statistics