X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 5D36AD1D23B for ; Wed, 31 Mar 2004 05:45:35 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 48603-06 for ; Wed, 31 Mar 2004 01:45:34 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 68AFAD1D206 for ; Wed, 31 Mar 2004 01:45:33 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i2V5jVJk029323; Wed, 31 Mar 2004 00:45:32 -0500 (EST) To: Rob Fielding Cc: pgsql-admin@postgresql.org Subject: Re: PG 7.2.4 and waiting backends In-reply-to: <40695D5C.7090101@dsvr.net> References: <40695D5C.7090101@dsvr.net> Comments: In-reply-to Rob Fielding message dated "Tue, 30 Mar 2004 12:43:24 +0100" Date: Wed, 31 Mar 2004 00:45:31 -0500 Message-ID: <29322.1080711931@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/401 X-Sequence-Number: 12970 Rob Fielding writes: > The intention is to migrate the DB from 7.2 to a later version. The > interim has been to get up to the latest 7.2.4 release inorder to > circumvent a vacuumdb corner case which was resulting in a FULL failing. Hmm ... why do you feel that you have to do a VACUUM FULL before you can dump and reload to go to a later version? AFAICS a vacuum in such a context is just a waste of cycles. It's certainly not going to reduce the size of the dump. The problems you are describing sound like index bloat to me. If the real issue is you haven't got enough disk space to do the dump, I'd suggest dropping all your indexes, after making notes so you can recreate them after finishing the upgrade. regards, tom lane