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

Re: Revitalising VACUUM FULL for 8.3

From: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
To: Hannu Krosing <hannu(at)skype(dot)net>
Cc: Zeugswetter Andreas ADI SD <ZeugswetterA(at)spardat(dot)at>,Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Revitalising VACUUM FULL for 8.3
Date: 2007-03-02 03:30:49
Message-ID: 20070302033048.GB15006@nasby.net (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Mar 01, 2007 at 04:54:44PM +0200, Hannu Krosing wrote:
> > > I was not suggesting that we remove visible rows through truncation.
> > 
> > Sure, unless you suggest to not truncate during this vacuum run ?
> > But we are talking about vacuum full, so truncation is essential.
> > 
> > It was suggested to do a dummy null update to move live tuples up front.
> > The old version is still visible for serializable txns.
> 
> There should probably be a wait-other-trxs to finish stage between
> COMPACT and 2nd VACUUM if truncation at this cycle is absolutely needed

Or you could just do a vacuum a bit later. If we've also got the DSM at
that point, vacuum should be fast.
-- 
Jim Nasby                                            jim(at)nasby(dot)net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)

In response to

pgsql-hackers by date

Next:From: Jim C. NasbyDate: 2007-03-02 03:36:18
Subject: Re: Revitalising VACUUM FULL for 8.3
Previous:From: Jeff DavisDate: 2007-03-02 01:26:41
Subject: Re: SOC & user quotas

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