X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 133339DC973 for ; Tue, 20 Dec 2005 10:52:36 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 92342-04 for ; Tue, 20 Dec 2005 10:52:40 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id A40D39DC89E for ; Tue, 20 Dec 2005 10:52:33 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id jBKEqZmF028967; Tue, 20 Dec 2005 09:52:35 -0500 (EST) To: Boguk Maxim cc: "'Gourish Singbal'" , pgsql-admin@postgresql.org Subject: Re: Some strange issues with VACUUM on one table. In-reply-to: <291ABF6CBE162F45B006AFF7AB770B8806F8A7C3@office.rambler.stack.net> References: <291ABF6CBE162F45B006AFF7AB770B8806F8A7C3@office.rambler.stack.net> Comments: In-reply-to Boguk Maxim message dated "Tue, 20 Dec 2005 16:02:00 +0300" Date: Tue, 20 Dec 2005 09:52:35 -0500 Message-ID: <28966.1135090355@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.018 required=5 tests=[AWL=0.018] X-Spam-Score: 0.018 X-Spam-Level: X-Archive-Number: 200512/219 X-Sequence-Number: 19939 Boguk Maxim writes: > I trying understand why vacuum analyze do not work at all. I think either you're not actually applying vacuum analyze at all (better double-check your daily maintenance script), or you're somehow managing to apply it at a time when it can't remove old rows because there's still an open transaction that might be able to see those rows. The latter theory doesn't really explain continuing table growth over time, though, unless you've got a transaction that's been sitting open the entire time. regards, tom lane