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 A4497329F8D for ; Mon, 18 Oct 2004 01:39:27 +0100 (BST) 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 74177-07 for ; Mon, 18 Oct 2004 00:39:15 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id A24AB329D9C for ; Mon, 18 Oct 2004 01:39:18 +0100 (BST) 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 i9I0dBc2015106; Sun, 17 Oct 2004 20:39:11 -0400 (EDT) To: Gaetano Mendola Cc: "pgsql-admin@postgresql.org" Subject: Re: Single table vacuum full different when vacuum full the whole database In-reply-to: <417309C0.4020100@bigfoot.com> References: <417309C0.4020100@bigfoot.com> Comments: In-reply-to Gaetano Mendola message dated "Mon, 18 Oct 2004 02:09:36 +0200" Date: Sun, 17 Oct 2004 20:39:11 -0400 Message-ID: <15105.1098059951@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/208 X-Sequence-Number: 15201 Gaetano Mendola writes: > it seems that a vacuum full on the whole DB is more aggressive. It is not. A much more plausible theory is that this is the result of concurrent changes to the table. It is clear from the "dead row versions" stats that there were concurrent transactions ... regards, tom lane