Skip site navigation (1) Skip section navigation (2)

Re: "unexpected EOF" messages

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: (view raw, whole thread or download thread mbox)
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

In response to


pgsql-hackers by date

Next:From: Merlin MoncureDate: 2012-05-03 14:18:27
Subject: Re: How hard would it be to support LIKE in return declaration of generic record function calls ?
Previous:From: Tom LaneDate: 2012-05-03 14:13:53
Subject: Re: ALTER DATABASE and datallowconn

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group