Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id D4EA42E003B for ; Mon, 19 May 2008 16:04:44 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 14318-04 for ; Mon, 19 May 2008 16:04:39 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by developer.postgresql.org (Postfix) with ESMTP id 933982E0031 for ; Mon, 19 May 2008 16:04:41 -0300 (ADT) Received: by yw-out-2324.google.com with SMTP id 3so1221600ywj.73 for ; Mon, 19 May 2008 12:04:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=czbvbcyhhfxQBi95pf42hFM2uVJzogTZlyTrN7aY4ac=; b=bUTZCkPzwU/GjIUkopp8oHUfyIgmCCaxO32DjYA/F7pP5+umXF3qJO7kCnEyd9CEvEqblru/pqtc+NhoqMfxFUvCbtdr8hW884BM+7PXM4Fcgm44fwUYrOcmwggiKoQkt2UYm3kfczg0guscIdgSwQoDSDVEShDovPvf4A0tm8U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=QoqQqv+qRUCC4TYPKsvfOhcCBFwDesJTYxFGYkh8w7cHk+bJAp9LaTZ6iGQbkp3fIs9veGAN+fqe2srOtq0ge7TXJDEe4N1y8tZA2G0jSxomO+kVN9/tOaiXbijiqUq6UajOWE+r6BMlJEhsLWt1NX7AerrCTBJYMynblM2cS3E= Received: by 10.150.69.41 with SMTP id r41mr6727603yba.126.1211223880803; Mon, 19 May 2008 12:04:40 -0700 (PDT) Received: by 10.150.53.20 with HTTP; Mon, 19 May 2008 12:04:40 -0700 (PDT) Message-ID: <4544e0330805191204g1df08313j6bcadf71a8be529f@mail.gmail.com> Date: Mon, 19 May 2008 14:04:40 -0500 From: "Peter Koczan" To: pgsql-admin@postgresql.org Subject: old, dead connections? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.75 tagged_above=0 required=5 tests=AWL=-0.750, WEIRD_PORT=1.499 X-Spam-Level: X-Archive-Number: 200805/163 X-Sequence-Number: 29247 Hi all, I'm looking to upgrade a server to postgres 8.3, but there's one connection that's being problematic. It continually says it's UPDATE'ing, but it's been at it for weeks now, and while the database is big, it shouldn't take weeks. Even weirder is that it looks like the client-side connection died a long time ago. [root@haddock] ~ $ ps axvw | grep post 330 pts/0 S+ 0:00 0 75 3820 648 0.0 grep post 14321 ? S 0:00 9 3274 1056081 20428 0.6 /s/postgresql-8.2.6/bin/postgres -D /scratch.1/postgres/fsstudy-8.2 14323 ? Ss 19:31 16 3274 1055873 1036904 30.7 postgres: writer process 14324 ? Ss 0:00 0 3274 8257 1644 0.0 postgres: stats collector process 20459 pts/8 S+ 0:01 3 227 5480 3444 0.1 /s/postgresql/bin/psql -h haddock -p 5432 fsstudy 20460 ? Ss 2295:51 27 3274 1057221 1045304 31.0 postgres: nitina fsstudy haddock.cs.wisc.edu(50957) idle 32247 ? Rs 17051:22 1 3274 1056653 1043964 30.9 postgres: nitina fsstudy haddock.cs.wisc.edu(41114) UPDATE [root@haddock] ~ $ netstat Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 haddock.cs.wisc.:postgresql haddock.cs.wisc.edu:50957 ESTABLISHED tcp 0 208 haddock.cs.wisc.edu:ssh ator.cs.wisc.edu:46929 ESTABLISHED tcp 0 0 haddock.cs.wisc.edu:50957 haddock.cs.wisc.:postgresql ESTABLISHED udp 0 0 localhost:33544 localhost:33544 ESTABLISHED ... I'm fairly certain that the connections noted in netstat refer to the idle connection. So, I don't want to just kill the connection right now unless I'm certain it can be done safely. However, I'd like to deal with it as it's a potential impediment to the upgrade and it's taking up lots of CPU time on the machine. Any advice, or any idea of what's going on? Peter