pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <decibel@decibel.org>
To: Christopher Browne <cbbrowne@acm.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Cheaper VACUUMing
Date: Sun, 23 Jan 2005 16:18:38 -0600
Message-ID: <20050123221838.GC67721@decibel.org> (raw)
In-Reply-To: <m38y6kzn4b.fsf_-_@knuth.knuth.cbbrowne.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>
	<m38y6kzn4b.fsf_-_@knuth.knuth.cbbrowne.com>

For reference, here's the discussion about this that took place on
hackers: http://lnk.nu/archives.postgresql.org/142.php 

On Sun, Jan 23, 2005 at 01:16:20AM -0500, Christopher Browne wrote:
> 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/;
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo@postgresql.org so that your
>       message can get through to the mailing list cleanly
> 

-- 
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?"



view thread (2+ messages)

Message-ID: <20050123221838.GC67721@decibel.org>
Permalink:  ../20050123221838.GC67721@decibel.org/
Also on:    postgresql.org/message-id/20050123221838.GC67721@decibel.org

 · 

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: decibel@decibel.org, cbbrowne@acm.org
  Subject: Re: Cheaper VACUUMing
  In-Reply-To: <20050123221838.GC67721@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