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

Re: Revitalising VACUUM FULL for 8.3

From: "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>,"Hannu Krosing" <hannu(at)skype(dot)net>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Revitalising VACUUM FULL for 8.3
Date: 2007-03-01 13:35:15
Message-ID: E1539E0ED7043848906A8FF995BDA57901CAFFCD@m0143.s-mxs.net (view raw or flat)
Thread:
Lists: pgsql-hackers
> 		-- start the VACUUM from the first non-filled block
> 
> So if we do this, we wouldn't need to worry about HOT tuples 
> at all, nor would we need to wait until all transactions are gone.

You need to wait until you are allowed to truncate if you want
concurrency.
Or a concurrent scan might miss a row, because the visible tuple got
truncated away.

Andreas

In response to

Responses

pgsql-hackers by date

Next:From: Hannu KrosingDate: 2007-03-01 13:40:04
Subject: Re: Revitalising VACUUM FULL for 8.3
Previous:From: Joshua D. DrakeDate: 2007-03-01 13:33:51
Subject: Re: Postgres Replication

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