Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 411C164FD69 for ; Thu, 6 Nov 2008 07:57:14 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 14982-05 for ; Thu, 6 Nov 2008 07:57:13 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.mnc.ch (62-2-77-205.static.cablecom.ch [62.2.77.205]) by mail.postgresql.org (Postfix) with ESMTP id B216D64FD34 for ; Thu, 6 Nov 2008 07:57:13 -0400 (AST) Received: from localhost (mail2.mnc.ch [127.0.0.1]) by mail.mnc.ch (Postfix) with ESMTP id 8EB0223079 for ; Thu, 6 Nov 2008 11:57:10 +0000 (GMT) X-Virus-Scanned: amavisd-new at mnc.ch Received: from mail.mnc.ch ([127.0.0.1]) by localhost (mail2.mnc.ch [127.0.0.1]) (amavisd-new, port 10025) with ESMTP id PPxqS5Imasqs for ; Thu, 6 Nov 2008 11:57:10 +0000 (GMT) Received: from meuh.localdomain (62-2-77-204.static.cablecom.ch [62.2.77.204]) by mail.mnc.ch (Postfix) with ESMTP id 112C523073 for ; Thu, 6 Nov 2008 11:57:10 +0000 (GMT) Received: by meuh.localdomain (Postfix, from userid 1000) id EA71A183537; Thu, 6 Nov 2008 12:57:09 +0100 (CET) To: pgsql-performance@postgresql.org Subject: Re: server space increasing very fast but transaction are very low References: <551154.82667.qm@web8405.mail.in.yahoo.com> <4912CF3E.90801@archonet.com> From: Guillaume Cottenceau X-Hashcash: 1:20:081106:pgsql-performance@postgresql.org::tBshFqMV5PxXKc0e:000000000000000000000000000001a2q Date: Thu, 06 Nov 2008 12:57:09 +0100 In-Reply-To: <4912CF3E.90801@archonet.com> (Richard Huxton's message of "Thu\, 06 Nov 2008 11\:04\:30 +0000") Message-ID: <8763n1jcdm.fsf@mnc.ch> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Archive-Number: 200811/25 X-Sequence-Number: 31756 Richard Huxton writes: > I'm guessing what you've got is a table that's not being vacuumed > because you've had a transaction that's been open for weeks. Or because no vacuuming at all is performed on this table (no autovacuum and no explicit VACUUM on database or table). -- Guillaume Cottenceau