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

From Robert Haas
Subject Re: [PROPOSAL] Client Log Output Filtering
Date
Msg-id CA+TgmoY1wjAmeOhW005a6EQmSHaH6Aj7ftSF9sdxax+M7bktVw@mail.gmail.com
Whole thread Raw
In response to Re: [PROPOSAL] Client Log Output Filtering  (David Steele <david@pgmasters.net>)
Responses Re: [PROPOSAL] Client Log Output Filtering
List pgsql-hackers
On Mon, Feb 1, 2016 at 7:24 PM, David Steele <david@pgmasters.net> wrote:
> On 2/1/16 5:25 PM, Alvaro Herrera wrote:
>> David Steele wrote:
>
>>> 2) There would be two different ways to suppress client messages but I was
>>> hoping to only have one.
>>
>> I think they are two different things actually.
>
> Fair enough - that was my initial reaction as well but then I thought
> the other way would be better.
>
>> I'm closing this as returned with feedback.
>
> I have attached a patch that adds an ereport() macro to suppress client
> output for a single report call (applies cleanly on 1d0c3b3).  I'll also
> move it to the next CF.

I don't see any reason not to accept this.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Raising the checkpoint_timeout limit
Next
From: Robert Haas
Date:
Subject: Re: Raising the checkpoint_timeout limit