From: Jim C. Nasby <decibel@decibel.org>
To: Greg Stark <gsstark@mit.edu>
Cc: Dawid Kuroczko <qnex42@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Sat, 22 Jan 2005 14:10:49 -0600
Message-ID: <20050122201049.GR67721@decibel.org> (raw)
In-Reply-To: <87brbh753e.fsf@stark.xeocode.com>
References: <41F144FE.30902@outputservices.com>
<41F14758.4030602@outputservices.com>
<20050122.121300.41631131.t-ishii@sra.co.jp>
<758d5e7f050122011713f9e27f@mail.gmail.com>
<758d5e7f0501220518477cedfa@mail.gmail.com>
<87brbh753e.fsf@stark.xeocode.com>
From http://developer.postgresql.org/todo.php:
Maintain a map of recently-expired rows
This allows vacuum to reclaim free space without requiring a sequential
scan
On Sat, Jan 22, 2005 at 12:20:53PM -0500, Greg Stark wrote:
> Dawid Kuroczko <qnex42@gmail.com> writes:
>
> > Quick thought -- would it be to possible to implement a 'partial VACUUM'
> > per analogiam to partial indexes?
>
> No.
>
> But it gave me another idea. Perhaps equally infeasible, but I don't see why.
>
> What if there were a map of modified pages. So every time any tuple was marked
> deleted it could be marked in the map as modified. VACUUM would only have to
> look at these pages. And if it could mark as free every tuple that was marked
> as deleted then it could unmark the page.
>
> The only downside I see is that this could be a source of contention on
> multi-processor machines running lots of concurrent update/deletes.
>
> --
> greg
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
--
Jim C. Nasby, Database Consultant decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
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: decibel@decibel.org, gsstark@mit.edu, qnex42@gmail.com
Subject: Re: PostgreSQL clustering VS MySQL clustering
In-Reply-To: <20050122201049.GR67721@decibel.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