Re: Eliminating VACUUM FULL WAS: remove flatfiles.c - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Eliminating VACUUM FULL WAS: remove flatfiles.c
Date
Msg-id 20090904192818.GL5603@alvh.no-ip.org
Whole thread Raw
In response to Re: Eliminating VACUUM FULL WAS: remove flatfiles.c  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: Eliminating VACUUM FULL WAS: remove flatfiles.c
List pgsql-hackers
Joshua D. Drake escribió:
> On Fri, 2009-09-04 at 15:10 -0400, Tom Lane wrote:
> > Robert Haas <robertmhaas@gmail.com> writes:
> > > I'm confused.  Are you saying that pg_class will never get bloated, so
> > > we don't need a way to debloat it?  I realize that with HOT bloat is
> > > much less of a problem than it used to be, but surely it's not
> > > altogether impossible...
> > 
> > Well, it's certainly *possible*, I'm just questioning the assertion that
> > it's necessarily a common situation.
> 
> Depends on your definition of common. It is very easy for someone to
> blow away their vacuum settings in such a way that it will become
> bloated pretty quick.

No problem, just CLUSTER that table same as today.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Eliminating VACUUM FULL WAS: remove flatfiles.c
Next
From: Tom Lane
Date:
Subject: Re: Eliminating VACUUM FULL WAS: remove flatfiles.c