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

Re: Broken pipes

From: "mike sears" <matrix(at)quadrent(dot)net>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Broken pipes
Date: 2001-10-27 05:01:07
Message-ID: 000f01c15ea4$6385b8c0$a8be5bd1@neutrino (view raw, whole thread or download thread mbox)
Lists: pgsql-general
I dunno if this makes any differnec or not, but we use php to interface w/
postgress. Could this also have anything to do with this problem?

as well would this surpression be in the current snapshots?


----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "mike sears" <matrix(at)quadrent(dot)net>
Cc: <pgsql-general(at)postgresql(dot)org>
Sent: 26 October, 2001 7:30 PM
Subject: Re: Broken pipes

> "mike sears" <matrix(at)quadrent(dot)net> writes:
> > pq_recvbuf: unexpected EOF on client connection
> This indicates that you have clients that are disconnecting
> ungracefully, but it doesn't tell us much about why.
> One recently-understood possibility is that if you are using psql
> with password authentication, then psql doesn't prompt you for a
> password until it's tried and failed to connect without.  That
> failure provokes one of these messages.  (For 7.2, we've hacked the
> postmaster to suppress the log message in that case.)
> Otherwise you have misbehaving client-side software.  I think that
> the ODBC driver is known not to disconnect gracefully, but I don't
> know of any other problems that would cause this, short of client
> crashes.
> regards, tom lane
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?

In response to


pgsql-general by date

Next:From: Keary SuskaDate: 2001-10-27 06:06:01
Subject: Re: Broken pipes
Previous:From: Mark kirkwoodDate: 2001-10-27 03:14:17
Subject: On Distributions In 7.2 (Longish)

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