Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id B4E909F9713 for ; Fri, 9 Nov 2007 18:44:43 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 79869-01-6 for ; Fri, 9 Nov 2007 18:44:33 -0400 (AST) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.228]) by postgresql.org (Postfix) with ESMTP id 384929FA36F for ; Fri, 9 Nov 2007 18:41:39 -0400 (AST) Received: by wr-out-0506.google.com with SMTP id 68so429797wri for ; Fri, 09 Nov 2007 14:41:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=203hg36SKlj1dLP3WgX655jasS6a45lHdQhMtJwqYiY=; b=QoYoE3VLvJ9fOzGLP+AiQxkprjHUK0kLVbM4b7uiy8tGRfO56V51Q1wLnLkrknhABdVJyv3nddBcmaoqUC/1ATNDJ22DVrFduxsqRuGkv9YR1k5koFtSuPYV46M/QCJ+sUugv4gpIv6coRNhqpjZgetFNQnCDB3Iy0ffNEhFRrI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JaH59oI863U+S7QdJTUIWoX7MbfJq+MqT8JNvray9H9tUbFzccOChvE6D+n5wH2vu8R6QGcKXoAhG0usTprtd09FCJRUgNKUg9twjLSp7kjtRFaUCJtbIbl++30kOTAW/Eq0Hczh9IfG0xyvocumL1WBtC/5NUUItzVl49oN2gE= Received: by 10.66.219.11 with SMTP id r11mr236758ugg.1194648094538; Fri, 09 Nov 2007 14:41:34 -0800 (PST) Received: by 10.67.95.18 with HTTP; Fri, 9 Nov 2007 14:41:34 -0800 (PST) Message-ID: Date: Fri, 9 Nov 2007 16:41:34 -0600 From: "Scott Marlowe" To: "Tena Sakai" Subject: Re: idle in transaction...unexpected EOF on client connection Cc: pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/85 X-Sequence-Number: 27328 On Nov 9, 2007 4:36 PM, Tena Sakai wrote: > Hi Scott, > > > > Most likely what is happening is that you have a firewall between your > > app and your db server that is closing idle connections after x minutes. > > Thanks for your comment. > > I hate to be disagreeable, but the app and postgres are running > on the same computer. The app is a java program using jdbc to > issue postgres commands. However, I see the same message via > psql (on the same machine). Hmmm. Well, when you see an error like unexpected EOF on client connection then that means that the client "disappeared" without closing the connection, or the network connection went away. Either way, the pgsql backend was still alive, and tried to send something to the client, and the client wasn't there. I.e. the problem isn't generally a postgresql problem, it's a client problem. So, the more info about the client app the better chance of fixing it. Note that if you've got a lot of "idle in transactions" connections, that's a bad thing because it prevents postgresql from being properly vacuumed. Most connection managers can be set to NOT issue a begin as part of a connection reset when returning it to the pool.