Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f7LKieP75216 for ; Tue, 21 Aug 2001 16:44:40 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f7LKiSY10621; Tue, 21 Aug 2001 16:44:28 -0400 (EDT) To: "Josh Berkus" cc: pgsql-sql@postgresql.org Subject: Re: Should I worry? In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Tue, 21 Aug 2001 12:35:44 -0700" Date: Tue, 21 Aug 2001 16:44:28 -0400 Message-ID: <10618.998426668@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200108/280 X-Sequence-Number: 4527 "Josh Berkus" writes: > Do I need to worry about this: > pq_flush: send() failed: Broken pipe > ... which appears in the log intermittently? Looks like the trace of a client disconnecting ungracefully (mid-query). If you're not aware of any client-side failures in your setup then you should perhaps look more closely, but otherwise this is not something to worry about. The backend will roll back its transaction and close up shop just fine. I think we have a TODO item to suppress multiple occurrences of this log message, but otherwise that stuff works fine AFAIK. regards, tom lane