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 3F2A7329EFC for ; Mon, 18 Oct 2004 01:50:01 +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 77129-08 for ; Mon, 18 Oct 2004 00:49:54 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 42B28329D9C for ; Mon, 18 Oct 2004 01:49:57 +0100 (BST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i9I0nsJ7079812 for ; Mon, 18 Oct 2004 00:49:54 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i9I0nq3G079804 for pgsql-admin@postgresql.org; Mon, 18 Oct 2004 00:49:52 GMT From: Gaetano Mendola X-Newsgroups: comp.databases.postgresql.admin Subject: Re: Single table vacuum full different when vacuum full the whole Date: Mon, 18 Oct 2004 02:49:52 +0200 Organization: PYRENET Midi-pyrenees Provider Lines: 32 Message-ID: <41731330.9090105@bigfoot.com> References: <417309C0.4020100@bigfoot.com> <15105.1098059951@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@pyrenet.fr To: Tom Lane User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en In-Reply-To: <15105.1098059951@sss.pgh.pa.us> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime To: pgsql-admin@postgresql.org 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/209 X-Sequence-Number: 15202 Tom Lane wrote: > 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 ... That is the more updated/inserted table, and yes there were some concurrent transaction but, is it plausible that 82 dead rows were responsible of grab 26000 index row: INFO: index "ua_user_data_exp_id_user_key" now contains 34438 row versions in 886 pages DETAIL: 27488 index row versions were removed. instead of: INFO: index "ua_user_data_exp_id_user_key" now contains 34519 row versions in 886 pages DETAIL: 1362 index row versions were removed. Regards Gaetano Mendola