Skip site navigation (1) Skip section navigation (2)

Re: VACUUM FULL out of memory

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: "Holger Hoffstaette" <holger(at)wizards(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: VACUUM FULL out of memory
Date: 2008-01-07 17:27:53
Message-ID: (view raw or whole thread)
Lists: pgsql-hackers
Hash: SHA1

On Mon, 07 Jan 2008 17:33:53 +0100
"Holger Hoffstaette" <holger(at)wizards(dot)de> wrote:

> On Mon, 07 Jan 2008 10:57:53 -0500, Andrew Sullivan wrote:
> > Note that you should almost never use VACUUM FULL unless you've
> > really messed things up.  I understand from the thread that you're
> > just testing things out right now.  But VACUUM FULL is not
> > something you should _ever_ need in production, if you've set
> > things up correctly.
> Then why does it exist? Is it a historical leftover? If it is
> only needed for emergency, should it not have a different name?
> Just curious..

There are times when it is required, usually when people don't
configure normal vacuum/autovacuum correctly.


Joshua D. Drake

> Holger
> ---------------------------(end of
> broadcast)--------------------------- TIP 4: Have you searched our
> list archives?

- -- 
The PostgreSQL Company: Since 1997, 
Sales/Support: +1.503.667.4564   24x7/Emergency: +1.800.492.2240
Donate to the PostgreSQL Project:
SELECT 'Training', 'Consulting' FROM vendor WHERE name = 'CMD'

Version: GnuPG v1.4.6 (GNU/Linux)


In response to

pgsql-hackers by date

Next:From: Markus SchiltknechtDate: 2008-01-07 18:16:35
Subject: Re: Dynamic Partitioning using Segment Visibility Maps
Previous:From: Joshua D. DrakeDate: 2008-01-07 17:10:24
Subject: Re: Bug: Unreferenced temp tables disables vacuum to update xid

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group