| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
| Cc: | "Campbell, Lance" <lance(at)uiuc(dot)edu>, "Tena Sakai" <tsakai(at)gallo(dot)ucsf(dot)edu>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: idle in transaction...unexpected EOF on client connection |
| Date: | 2007-11-09 22:33:47 |
| Message-ID: | dcc563d10711091433u2a7175fai3c38cea7f0177baf@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Nov 9, 2007 4:29 PM, Alvaro Herrera <alvherre(at)commandprompt(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tena Sakai | 2007-11-09 22:36:13 | Re: idle in transaction...unexpected EOF on client connection |
| Previous Message | Alvaro Herrera | 2007-11-09 22:29:16 | Re: idle in transaction...unexpected EOF on client connection |