X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 5C5C656392 for ; Tue, 15 Mar 2005 15:32:36 +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 76511-06 for ; Tue, 15 Mar 2005 15:32:35 +0000 (GMT) Received: from mail.libertyrms.com (unknown [207.219.45.62]) by svr1.postgresql.org (Postfix) with ESMTP id DC8CC559C2 for ; Tue, 15 Mar 2005 15:32:33 +0000 (GMT) Received: from dba5.int.libertyrms.com ([10.1.3.44]) by mail.libertyrms.com with esmtp (Exim 4.22) id 1DBE2A-0005xP-6y for pgsql-admin@postgresql.org; Tue, 15 Mar 2005 10:32:38 -0500 Message-ID: <42370015.5020404@ca.afilias.info> Date: Tue, 15 Mar 2005 10:32:37 -0500 From: Brad Nicholson User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Performance Question References: In-Reply-To: Content-Type: text/plain; charset=windows-1250; format=flowed Content-Transfer-Encoding: 7bit X-SA-Exim-Mail-From: bnichols@ca.afilias.info X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.02 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200503/224 X-Sequence-Number: 16722 Werner vd Merwe wrote: >Output of VACUUM ANALYSE VERBOSE pg_listener: > >Query OK, 0 rows affected (0.06 sec) >INFO: vacuuming "pg_catalog.pg_listener" >INFO: "pg_listener": found 0 removable, 0 nonremovable row versions in 0 >pages >INFO: analyzing "pg_catalog.pg_listener" >INFO: "pg_listener": 0 pages, 0 rows sampled, 0 estimated total rows > > > No problems there. >At any given time we have between 10 and 20 IDLE connections. > > > How long have the transactions been IDLE for? Do the IDLE transactions have any locks on anything (check pg_locks)? I suspect that (gently) killing the IDLE transactions that are sitting around doing nothing will prevent you from having to restart the postmaster. -- Brad Nicholson Database Administrator, Afilias Canada Corp. >-----Original Message----- >From: pgsql-admin-owner@postgresql.org >[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Brad Nicholson >Sent: 14 March 2005 07:10 PM >To: PgSQL Admin >Subject: Re: [ADMIN] Performance Question > >I'm wondering if long running transacations might be the cause (you'll >likely want to do this while perfomance is suffering). > >Have a look at pg_stat_activity and see if there are any long running >transacations (or any idle transactions). > >I'd also be curious to see the output of the following: > >VACUUM ANALYZE VERBOSE pg_listener; > > >