| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "unexpected EOF" messages |
| Date: | 2012-05-03 14:17:57 |
| Message-ID: | 22514.1336054677@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2012-05-03 14:18:27 | Re: How hard would it be to support LIKE in return declaration of generic record function calls ? |
| Previous Message | Tom Lane | 2012-05-03 14:13:53 | Re: ALTER DATABASE and datallowconn |