> 		-- 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

• Re: Revitalising VACUUM FULL for 8.3 at 2007-03-01 13:14:14 from Simon Riggs

Responses

• Re: Revitalising VACUUM FULL for 8.3 at 2007-03-01 13:41:44 from Simon Riggs

pgsql-hackers by date

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