X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 542653CC4ED for ; Fri, 17 Dec 2004 22:20:53 +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 93384-08 for ; Fri, 17 Dec 2004 22:20:46 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 4F2543CC491 for ; Fri, 17 Dec 2004 22:20:47 +0000 (GMT) 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 iBHMKl8T024693; Fri, 17 Dec 2004 17:20:47 -0500 (EST) To: Pailloncy Jean-Gerard Cc: pgsql-performance@postgresql.org Subject: Re: Error in VACUUM FULL VERBOSE ANALYZE (not enough memory) In-reply-to: References: <3D4B6E62-5055-11D9-96E2-000A95DE2550@ifrance.com> Comments: In-reply-to Pailloncy Jean-Gerard message dated "Fri, 17 Dec 2004 22:59:07 +0100" Date: Fri, 17 Dec 2004 17:20:47 -0500 Message-ID: <24692.1103322047@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.004 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200412/232 X-Sequence-Number: 9607 Pailloncy Jean-Gerard writes: > Update to my case: > I drop and recreate the index and there was no problem this time. > Strange... Well, that time there wasn't actually any work for VACUUM FULL to do. I think the bloat is probably driven by having to move a lot of rows in order to shrink the table. That means creating and deleting a lot of index entries. regards, tom lane