| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Petr Jelinek <petr(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, 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-11 14:56:06 |
| Message-ID: | 56E2DC86.8040006@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/10/16 9:51 AM, Tom Lane wrote:
> The patch is evidently modeled on errhidestmt and errhidectx, which are
> making the same assumption for their fields.
>
> I wonder whether, instead of continuing to proliferate random bool fields
> in struct ErrorData, we oughta replace them all with an "int flags" field.
> That's probably material for a separate patch though.
There are currently six boolean flags (if you include my new one) that
all relate to visibility in one way or another. Combining them into a
"flags" field makes sense to me.
I'll submit a proposal to hackers after 9.6 to make this change.
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2016-03-11 14:57:53 | Re: dblink: add polymorphic functions. |
| Previous Message | David Steele | 2016-03-11 14:52:26 | Re: [PROPOSAL] Client Log Output Filtering |