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

Re: [HACKERS] Resurrecting per-page cleaner for btree

From: Hannu Krosing <hannu(at)skype(dot)net>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Csaba Nagy <nagy(at)ecircle-ag(dot)com>,postgres hackers <pgsql-hackers(at)postgresql(dot)org>,ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>,pgsql-patches(at)postgresql(dot)org, teramoto(dot)junji(at)lab(dot)ntt(dot)co(dot)jp
Subject: Re: [HACKERS] Resurrecting per-page cleaner for btree
Date: 2006-07-26 21:29:17
Message-ID: 1153949357.2928.32.camel@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Ühel kenal päeval, K, 2006-07-26 kell 23:02, kirjutas Martijn van
Oosterhout:
> On Wed, Jul 26, 2006 at 12:47:57PM -0400, Greg Stark wrote:
> > Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> > 
> > > So far, the case hasn't been made for retail vacuum even ignoring the
> > > not-so-immutable-function risk.
> > 
> > Well the desire for it comes from a very well established need for dealing
> > with extremely large tales with relatively small hot spots. The basic problem
> > being that currently the cost of vacuum is proportional to the size of the
> > table rather than the amount of dead space. There's no link between those
> > variables (at least in one direction) and any time they're far out of whack it
> > means excruciating pain for the DBA.
> 
> I thought the suggested solution for that was the dead space map. That
> way vacuum can ignore parts of the table that havn't changed...

It can ignore parts of the *table* but still has to scan full *indexes*.

-- 
----------------
Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia

Skype me:  callto:hkrosing
Get Skype for free:  http://www.skype.com


In response to

Responses

pgsql-hackers by date

Next:From: Bort, PaulDate: 2006-07-26 21:29:38
Subject: Re: GUC with units, details
Previous:From: Darcy BuskermolenDate: 2006-07-26 21:27:17
Subject: Re: [HACKERS] [PATCH] Provide 8-byte transaction IDs to user level

pgsql-patches by date

Next:From: Alvaro HerreraDate: 2006-07-26 21:35:42
Subject: Re: [HACKERS] [PATCH] Provide 8-byte transaction IDs to user level
Previous:From: Darcy BuskermolenDate: 2006-07-26 21:27:17
Subject: Re: [HACKERS] [PATCH] Provide 8-byte transaction IDs to user level

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