From: Scott Marlowe <scott.marlowe@gmail.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Campbell, Lance <lance@uiuc.edu>
Cc: Tena Sakai <tsakai@gallo.ucsf.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: idle in transaction...unexpected EOF on client connection
Date: Fri, 9 Nov 2007 16:33:47 -0600
Message-ID: <dcc563d10711091433u2a7175fai3c38cea7f0177baf@mail.gmail.com> (raw)
In-Reply-To: <20071109222916.GK7161@alvh.no-ip.org>
References: <FE44E0D7EAD2ED4BB2165071DB8E328C03062D82@egcrc-ex01.egcrc.org>
<B10E6810AC2A2F4EA7550D072CDE8760197DEC@SAB-FENWICK.sab.uiuc.edu>
<20071109222916.GK7161@alvh.no-ip.org>
On Nov 9, 2007 4:29 PM, Alvaro Herrera <alvherre@commandprompt.com> wrote:
> Campbell, Lance wrote:
> > I notice this in my log file as well. I do not have a fire wall that
> > would impact this.
>
> It could be a monitoring tool that's opening the socket to check whether
> Postgres is listening. If it connects then closes the socket without
> actually talking the PG protocol, this is exactly what you would see.
That might explain Lance's problem but not Tena's, since his (hers?)
are idle in transaction, which means the connection at least did a
begin; after connecting.
Also possible for Lance's is an application that isn't properly
closing its connections.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott.marlowe@gmail.com, alvherre@commandprompt.com, lance@uiuc.edu, tsakai@gallo.ucsf.edu
Subject: Re: idle in transaction...unexpected EOF on client connection
In-Reply-To: <dcc563d10711091433u2a7175fai3c38cea7f0177baf@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox