Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 4AF3B2EE4E3 for ; Fri, 13 Jan 2012 10:50:47 -0400 (AST) Received: from gwmta.wicourts.gov ([165.219.244.99] helo=gw.wicourts.gov) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RliSn-0001cE-Er for pgsql-performance@postgresql.org; Fri, 13 Jan 2012 14:50:46 +0000 Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Fri, 13 Jan 2012 08:50:27 -0600 Message-Id: <4F0FF04D0200002500044778@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Fri, 13 Jan 2012 08:50:21 -0600 From: "Kevin Grittner" To: "Mario Weilguni" , Subject: Re: auto vacuum, not working? References: <000301ccd1ec$167ab7d0$43702770$@devshock.com> <4F103F00.2080904@gmx.at> In-Reply-To: <4F103F00.2080904@gmx.at> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Pg-Spam-Score: -4.2 (----) X-Archive-Number: 201201/43 X-Sequence-Number: 46056 Mario Weilguni wrote: >> yesterday I delete about 200 million rows of a table >> How can I release the space used by deleted rows? >> Without block the table. > vacuum does not reclaim space, just marks tuples dead. You need > vacuum full. VACUUM FULL will lock the table, blocking all other access, and it can run for quite a while. If you expect to be adding 200 million new rows to the table in the foreseeable future, a regular VACUUM (or autovacuum) will make that space available for reuse by that table. The space won't show in the file system; it will still be allocated to the database but available for new rows. -Kevin