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

Re: PostgreSQL clustering VS MySQL clustering

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Dawid Kuroczko <qnex42(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: 2005-01-22 17:20:53
Message-ID: 87brbh753e.fsf@stark.xeocode.com (view raw or flat)
Thread:
Lists: pgsql-performance
Dawid Kuroczko <qnex42(at)gmail(dot)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


In response to

Responses

pgsql-performance by date

Next:From: Bruno Wolff IIIDate: 2005-01-22 18:41:24
Subject: Re: PostgreSQL clustering VS MySQL clustering
Previous:From: Dawid KuroczkoDate: 2005-01-22 13:18:27
Subject: PostgreSQL clustering VS MySQL clustering

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