From: Ralph Mason <ralph.mason@telogis.com>
To: pgsql-performance@postgresql.org
Subject: 'Real' auto vacuum?
Date: Wed, 31 Aug 2005 10:21:20 +1200
Message-ID: <4314DBE0.9070708@telogis.com> (raw)
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?
Ralph
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ralph.mason@telogis.com
Subject: Re: 'Real' auto vacuum?
In-Reply-To: <4314DBE0.9070708@telogis.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox