Re: Unexpected VACUUM FULL failure

From: Gregory Stark
To: "Simon Riggs"
Cc: "Tom Lane" , "Heikki Linnakangas" , "Alvaro Herrera" ,
Subject: Re: Unexpected VACUUM FULL failure
Date: 2007-08-10 23:20:47
Message-ID: [email protected]
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


"Simon Riggs" writes:

> It would be better to release 8.3 with a new, clean, fast implementation
> of VF, than to release it with code that we *think* is right, but has so
> far proved a source of some truly obscure bugs.

Well building a suitable replacement for VACUUM FULL is more work than I was
proposing. The no-op ALTER TABLE rebuild still has the disadvantage of
requiring 2x the space taken by the table (and potentially more if you have
large indexes).

I also think it's a safer course of action to create a new command, spend one
or two releases improving it until we're sure it meets everyone's needs, then
drop the old command.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-08-11 01:25:34 regexp_matches and regexp_split are inconsistent
Previous Message Tom Lane 2007-08-10 22:52:36 Re: regexp_split_to_array hangs backend