| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PROPOSAL] Client Log Output Filtering |
| Date: | 2016-02-02 00:24:48 |
| Message-ID: | 56AFF750.6030306@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Thanks!
--
-David
david(at)pgmasters(dot)net
| Attachment | Content-Type | Size |
|---|---|---|
| ereport-v2.patch | text/plain | 2.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2016-02-02 00:29:39 | Re: "using previous checkpoint record at" maybe not the greatest idea? |
| Previous Message | Tatsuo Ishii | 2016-02-02 00:23:28 | Re: Trigger.sgml |