pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Cheaper VACUUMing
Date: Sun, 23 Jan 2005 01:16:20 -0500
Message-ID: <m38y6kzn4b.fsf_-_@knuth.knuth.cbbrowne.com> (raw)
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>

A long time ago, in a galaxy far, far away, gsstark@mit.edu (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.

I was thinking the same thing after hearing fairly extensive
"pooh-poohing" of the notion of vacuuming based on all the pages in
the shared cache.

This "hot list page table" would probably need to be a hash table.  It
rather parallels the FSM, including the way that it would need to be
limited in size.
-- 
wm(X,Y):-write(X),write('@'),write(Y). wm('cbbrowne','gmail.com').
http://cbbrowne.com/info/lsf.html
Rules  of  the  Evil  Overlord  #57. "Before  employing  any  captured
artifacts  or machinery, I  will carefully  read the  owner's manual."
<http://www.eviloverlord.com/;



view thread (2+ messages)  latest in thread

Message-ID: <m38y6kzn4b.fsf_-_@knuth.knuth.cbbrowne.com>
Permalink:  ../m38y6kzn4b.fsf_-_@knuth.knuth.cbbrowne.com/
Also on:    postgresql.org/message-id/m38y6kzn4b.fsf_-_@knuth.knuth.cbbrowne.com

 · 

reply

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: cbbrowne@acm.org
  Subject: Re: Cheaper VACUUMing
  In-Reply-To: <m38y6kzn4b.fsf_-_@knuth.knuth.cbbrowne.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