Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id BD28C9FBF94 for ; Tue, 15 May 2007 20:16:27 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 94455-01 for ; Tue, 15 May 2007 20:16:23 -0300 (ADT) X-Greylist: whitelisted by SQLgrey-1.7.5 Received: from mail20.syd.optusnet.com.au (mail20.syd.optusnet.com.au [211.29.132.201]) by postgresql.org (Postfix) with ESMTP id 3F8169FBF9A for ; Tue, 15 May 2007 20:16:22 -0300 (ADT) Received: from www3.nicku.org (c211-30-174-44.farfl1.nsw.optusnet.com.au [211.30.174.44]) by mail20.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id l4FNGIoW006254; Wed, 16 May 2007 09:16:19 +1000 Received: from localhost (localhost.localdomain [127.0.0.1]) by www3.nicku.org (Postfix) with ESMTP id B2541246DE6; Wed, 16 May 2007 09:16:18 +1000 (EST) X-Virus-Scanned: amavisd-new at example.com Received: from www3.nicku.org ([127.0.0.1]) by localhost (www3.nicku.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I1yQmUp-HSTg; Wed, 16 May 2007 09:16:17 +1000 (EST) Received: by www3.nicku.org (Postfix, from userid 1000) id 32955246F5B; Wed, 16 May 2007 09:16:17 +1000 (EST) Date: Wed, 16 May 2007 09:16:17 +1000 From: Nick Urbanik To: pgsql-admin@postgresql.org Subject: Re: How overcome wait for vacuum full? Message-ID: <20070515231616.GH5264@nicku.org> References: <20070515221356.GG5264@nicku.org> <20070515225313.GV12731@alvh.no-ip.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qM81t570OJUP5TU/" Content-Disposition: inline In-Reply-To: <20070515225313.GV12731@alvh.no-ip.org> User-Agent: Mutt/1.4.2.2i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/123 X-Sequence-Number: 25443 --qM81t570OJUP5TU/ Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Thank you Alvaro, On 15/05/07 18:53 -0400, Alvaro Herrera wrote: >Instead of waiting a month for the time when you can take the >application offline (thus accumulating a month's worth of dead tuples), >run a non-full vacuum more often (say, once a day or more). It doesn't >lock the table so the app can continue to be online while it runs. Yes, it is vacuumed non-full regularly. However, for some reason, only a full vacuum will recover the space. >If you have too many dead tuples and are desperate to get the table in a >reasonable non-bloated state, try CLUSTER instead of VACUUM FULL. It >might finish faster. 1. If I am running vacuum full on the database as: vacuum full verbose; without specifying a table, if I interrupt it, will the vacuuming of the other tables that have already been vacuumed be undone? How far is vacuuming rolled back if I interrupt it in this case? 2. If I interrupt the vacuum, and run cluster, how long do you think cluster might take relative to a full vaccuum? Is it likely to save disk space? (since that is the aim rather than speeding things up) The value of reltuples and relpages for this table are: reltuples: 572208, relpages 187502 3. This is PostgreSQL 7.3.8. --=20 Nick Urbanik RHCE http://nicku.org nicku@nicku.org GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24 --qM81t570OJUP5TU/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFGSj9AFt/sW7udLCQRAh1QAKDAbwJDLFf852Q/rdAr0che3gWOVACdE8ie Eopv7PKNSfydHeH8vla2j2o= =ntsl -----END PGP SIGNATURE----- --qM81t570OJUP5TU/--