| From: | Petr Jelinek <petr(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PROPOSAL] Client Log Output Filtering |
| Date: | 2016-03-10 00:37:53 |
| Message-ID: | 56E0C1E1.1070109@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/02/16 05:02, Robert Haas wrote:
> On Mon, Feb 1, 2016 at 7:24 PM, David Steele <david(at)pgmasters(dot)net> wrote:
>>
>> 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.
>
Yes, the idea seems sane.
Looking at the code, this adds bool hide_from_client to edata which is
not initialized in errstart so that needs to be fixed.
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2016-03-10 00:42:21 | Re: statistics for array types |
| Previous Message | David Steele | 2016-03-10 00:29:10 | Re: Improving replay of XLOG_BTREE_VACUUM records |