Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 8E8912E003F for ; Sun, 30 Mar 2008 15:26:51 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 83198-04 for ; Sun, 30 Mar 2008 15:26:51 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by developer.postgresql.org (Postfix) with ESMTP id 0A31B2E002D for ; Sun, 30 Mar 2008 15:26:50 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id m38so1533756waf.5 for ; Sun, 30 Mar 2008 11:26:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=zJox0aFLEPok8IrZfePX+bdk2A3ENHQ8VS6FQN4vE8A=; b=mVZORS5WI5zbT5ccEQ/mZJNGDHBD0ezCpSOILmIdVe+58n1n6rt8S2P9uPv+yBj/84cjuiLJQPYEu37OCJbSv+wLNipgPXZ9/c+rwoO4IiX0qXK81xg68k/3bq482ttjCPGwlStaAsaBn/QTZNmqd5UQK4JfWjkKh5LoTkVwm3Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=M83LpJlWW3/eiz+/XMUCxcEqUsuui1GGZdHRADMKT0lomBjaz/XA0uhnHVCwG8zJt+L9f5hbqsvX8GUuGUhNIBfYb/nj9FBUDpaZNFEpmJmlNQ+rP0N+31rnScFGehn1S2nBO7q9hzDQco0LxndQj1RrIvtv80Y7tN+RROyZ3XQ= Received: by 10.114.156.1 with SMTP id d1mr8309196wae.68.1206901609970; Sun, 30 Mar 2008 11:26:49 -0700 (PDT) Received: by 10.114.102.14 with HTTP; Sun, 30 Mar 2008 11:26:49 -0700 (PDT) Message-ID: <2ca799770803301126p6facf429r108b06ca4e54440a@mail.gmail.com> Date: Sun, 30 Mar 2008 21:26:49 +0300 From: "Mikko Partio" To: "Tom Lane" Subject: Re: Vacuum full crash Cc: pgsql-admin@postgresql.org In-Reply-To: <10439.1206891635@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_13317_15446012.1206901609965" References: <2ca799770803291340p75d8a4e2o7dfd6c61e73270f6@mail.gmail.com> <21772.1206824718@sss.pgh.pa.us> <2ca799770803300356r185b1adbv2ab17c7cc8f212a7@mail.gmail.com> <10439.1206891635@sss.pgh.pa.us> X-Archive-Number: 200803/258 X-Sequence-Number: 28741 ------=_Part_13317_15446012.1206901609965 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Sun, Mar 30, 2008 at 6:40 PM, Tom Lane wrote: > It would be good to fix it I suppose, but what with VACUUM FULL being on > the edge of deprecation anyway, it's hard to muster enthusiasm for doing > a (probably) large additional amount of work on it, I think most > hackers would prefer to spend time on making it unnecessary than making > it more bulletproof. > Interesting. What is planned substitute for VACUUM FULL? CLUSTER? Regards Mikko ------=_Part_13317_15446012.1206901609965 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On Sun, Mar 30, 2008 at 6:40 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
It would be good to fix it I suppose, but what with VACUUM FULL being on
the edge of deprecation anyway, it's hard to muster enthusiasm for doing
a (probably) large additional amount of work on it,  I think most
hackers would prefer to spend time on making it unnecessary than making
it more bulletproof.


Interesting. What is planned substitute for VACUUM FULL? CLUSTER?

Regards

Mikko
------=_Part_13317_15446012.1206901609965--