Re: Brain dump: btree collapsing - Mailing list pgsql-hackers

From Curtis Faith
Subject Re: Brain dump: btree collapsing
Date
Msg-id 001601c2d341$01a5e720$5e043ac8@curtislaptop
Whole thread Raw
In response to Brain dump: btree collapsing  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Brain dump: btree collapsing
List pgsql-hackers
tom lane initially wrote:
> Restructuring the tree during page deletion
> -------------------------------------------
> 
> We will delete only completely-empty pages.  If we were to
> merge nearly-empty pages by moving data items from one page 
> to an adjacent one, this would imply changing the parent's 
> idea of the bounding key between them --- which is okay if we 
> are just deleting an internal key in the parent, but what if 
> the pages have different parent pages?

and a bit later wrote:
> My feeling is that what we need to fix now is index bloat during 
> normal operation.

How about doing deletion of partial pages with reorganization among
sibling pages only (where the parent pages are the same)? This avoids
the "messiness" of propogating the deletes to differing parent pages but
gets most of the value of reorganization.

ISTM, that a VACUUM that only reclaims empty pages will be helpful in
certain cases but won't help much at all in many other common "normal
operation" cases which would be helped by partial reorganization.

- Curtis




pgsql-hackers by date:

Previous
From: Curt Sampson
Date:
Subject: Re: location of the configuration files
Next
From: Christopher Browne
Date:
Subject: Re: location of the configuration files