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

'Real' auto vacuum?

From: Ralph Mason <ralph(dot)mason(at)telogis(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: 'Real' auto vacuum?
Date: 2005-08-30 22:21:20
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
This is a wild and crazy thought which I am sure is invalid for some 
good reason.

But why can't postgres just vacuum itself as it goes along?

When a row is orphaned it's added to a list of possibly available rows.  
When a new row is needed the list of possible rows is examined and the 
first one with a transaction id less then the lowest running transaction 
id is chosen to be the new row?  These rows can be in a heap so it's 
really fast to find one.

Like magic - no more vacuuming.  No more holes for people to fall into.

Is this an oversimplification of the problem?



pgsql-performance by date

Next:From: markDate: 2005-08-30 22:35:19
Subject: Re: 'Real' auto vacuum?
Previous:From: Chris BrowneDate: 2005-08-30 22:05:38
Subject: Re: When to do a vacuum for highly active table

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