| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "unexpected EOF" messages |
| Date: | 2012-05-03 14:49:41 |
| Message-ID: | CABUevEyKONjOKTmLUWnOAjrJ3rKD+PG1X0QLZVwVxV=L7q1BOQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 3, 2012 at 4:17 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
>> On Thu, May 3, 2012 at 1:26 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>> I had a request from a customer asking if we could make a switch to
>>> specifically disable the "unexpected EOF" message that fills lots of
>>> peoples logs.
>
>> Yes, if the new parameter allows a generic filter on multiple
>> user-specified message types.
>
> I agree with Simon --- a disable for that specific message seems like a
> kluge, and an ugly one at that. (The right solution for this customer
> is to fix their broken application.) But a generic filter capability
> might be useful enough to justify its keep.
Are you thinking basically "regexp against the main text", or
something else, when you say "generic filter capacity"?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-05-03 14:50:47 | Re: How hard would it be to support LIKE in return declaration of generic record function calls ? |
| Previous Message | Magnus Hagander | 2012-05-03 14:48:12 | Re: "unexpected EOF" messages |