Re: "unexpected EOF" messages

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "unexpected EOF" messages
Date: 2012-05-03 15:33:54
Message-ID: CA+TgmoaA_h_AipyFomfag_pBmHbJynLSpj-SzXxdfD9uRmve8A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 3, 2012 at 11:20 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Hey, maybe we could add a UUID to each ereport() call site ;-)

I can't help but feel we're designing a $10.00 solution to a $0.25
problem. I think I'd actually support adding something like a UUID to
every ereport and a filtering mechanism that works on that basis. But
let's face it: this particular message is exponentially more annoying
than average. We're basically forcing application developers to jump
through hoops to avoid filling the log with unnecessary chatter. I've
spent a bunch of time trying to get rid of them in various past jobs,
and I've never gotten any benefit out of having them. Maybe the
solution is to just demote that particular message to DEBUG1 and
declare that closing the connection is a perfectly sensible way for an
application to indicate that the conversation is over.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-05-03 15:34:33 Re: Torn page hazard in ginRedoUpdateMetapage()
Previous Message Alvaro Herrera 2012-05-03 15:20:32 Re: "unexpected EOF" messages