From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-performance@postgresql.org
Subject: Re: Autovacuum / full vacuum
Date: Tue, 17 Jan 2006 10:13:57 -0500
Message-ID: <20060117151357.GH21092@phlogiston.dyndns.org> (raw)
In-Reply-To: <dqitj2$27j3$1@news.hub.org>
References: <dqigaf$1b98$1@news.hub.org>
<m364ojrm4f.fsf@mobile.int.cbbrowne.com>
<dqitj2$27j3$1@news.hub.org>
On Tue, Jan 17, 2006 at 03:05:29PM +0100, Michael Riess wrote:
> There must be a way to implement a daemon which frees up space of a
> relation without blocking it too long.
Define "too long". If I have a table that needs to respond to a
SELECT in 50ms, I don't have time for you to lock my table. If this
were such an easy thing to do, don't you think the folks who came up
wit the ingenious lazy vacuum system would have done it?
Remember, a vacuum full must completely lock the table, because it is
physically moving bits around on the disk. So a SELECT can't happen
at the same time, because the bits might move out from under the
SELECT while it's running. Concurrency is hard, and race conditions
are easy, to implement.
A
--
Andrew Sullivan | ajs@crankycanuck.ca
A certain description of men are for getting out of debt, yet are
against all taxes for raising money to pay it off.
--Alexander Hamilton
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: ajs@crankycanuck.ca
Subject: Re: Autovacuum / full vacuum
In-Reply-To: <20060117151357.GH21092@phlogiston.dyndns.org>
* 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