X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5F1B08BA35B for ; Mon, 21 Feb 2005 03:50:15 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 31851-09 for ; Mon, 21 Feb 2005 03:50:01 +0000 (GMT) Received: from floppy.pyrenet.fr (news.pyrenet.fr [194.250.190.2]) by svr1.postgresql.org (Postfix) with ESMTP id 1C2B28BA333 for ; Mon, 21 Feb 2005 03:50:04 +0000 (GMT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id EEF3A31FEC; Mon, 21 Feb 2005 04:50:04 +0100 (MET) From: Christopher Browne X-Newsgroups: pgsql.performance Subject: Re: Effects of IDLE processes Date: Sun, 20 Feb 2005 22:18:31 -0500 Organization: cbbrowne Computing Inc Lines: 44 Message-ID: References: <200502181815.17000.jerome@gmanmi.tv> <4219304A.1070408@bigfoot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4 (Jumbo Shrimp, linux) Cancel-Lock: sha1:A1Jz91vU0k2XLUeqZYF5WHrapxQ= To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.345 tagged_above=0 required=5 tests=AWL, INFO_TLD X-Spam-Level: X-Archive-Number: 200502/281 X-Sequence-Number: 10610 After a long battle with technology, Gaetano Mendola , an earthling, wrote: > JM wrote: >> Hi ALL, >> >> I was wondering if there is a DB performance reduction if >> there are a lot of IDLE processes. >> >> 30786 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 32504 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 32596 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 1722 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 1724 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 3881 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 6332 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 6678 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 6700 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 6768 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 8544 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 8873 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 8986 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 9000 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 9010 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 9013 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 9016 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 9019 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> 9020 ? S 0:00 postgres: user1 gmadb 10.10.10.1 idle >> > In my experience not at all, you have to wonder if some of that are > "idle in transaction" that are really a pain in the @#$ I'd be concerned about "idle" processes insofar as they are holding on to _some_ memory that isn't shared. "idle in transaction" is quite another matter; long-running transactions certainly do lead to evil. When running Slony-I, for instance, "idle in transaction" means that pg_listener entries are being held onto so they cannot be vacuumed out, and that's only one example of a possible evil... -- (reverse (concatenate 'string "moc.liamg" "@" "enworbbc")) http://linuxdatabases.info/info/languages.html You know how most packages say "Open here". What is the protocol if the package says, "Open somewhere else"?