Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 32B099FBF53 for ; Tue, 15 May 2007 22:00:00 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 18272-02 for ; Tue, 15 May 2007 21:59:56 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id D89DB9FBC5A for ; Tue, 15 May 2007 21:59:56 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 937FC56457; Tue, 15 May 2007 19:59:55 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Tue, 15 May 2007 19:59:54 -0500 Date: Tue, 15 May 2007 19:59:54 -0500 From: "Jim C. Nasby" To: pgsql-admin@postgresql.org Subject: Re: How far does interrupting vacuum full rollback? Message-ID: <20070516005954.GC11533@nasby.net> References: <20070515233728.GB16021@nicku.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070515233728.GB16021@nicku.org> X-Operating-System: FreeBSD 6.1-RELEASE-p10 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.13 (2006-08-11) X-Hashcash: 1:20:070516:pgsql-admin@postgresql.org::7+6bR26xFkYFtHtw:00000000000 0000000000000000000000000/qG X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/131 X-Sequence-Number: 25451 On Wed, May 16, 2007 at 09:37:28AM +1000, Nick Urbanik wrote: > Dear Folks, > > I would like to interrupt this full vacuum run as: > > vacuum full verbose; > > which has vacuumed a number of tables. > > Will interrupting it (with Control-C) cause vacuuming of the previous > tables to be rolled back, or just the vacuuming of the current table? Just the current table. > WIll any of the work done on the current table remain if the vacuuming > process is interrupted? If it's had to cycle though the heap more than once due to running out of maintenance_work_mem (or whatever it's called in 7.3) then I believe some of the work will be saved. > This is PostgreSQL 7.3.8. You should strongly consider upgrading to 8.2 or at least 8.1. If nothing else at least get on the latest 7.3 version. -- Jim Nasby decibel@decibel.org EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)