Re: Brain dump: btree collapsing

From: Daniel Kalchev <daniel(at)digsys(dot)bg>
To: Justin Clift <justin(at)postgresql(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Brain dump: btree collapsing
Date: 2003-02-13 08:16:36
Message-ID: 200302130816.h1D8GaY18052@dcave.digsys.bg
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>>Justin Clift said:
> <snip>
> > In theory, if we find recyclable page(s) at the physical end of the index,
> > we could truncate the file (ie, give the space back to the filesystem)
> > instead of reporting these pages to FSM. I am not sure if this is worth
> > doing --- in most cases it's likely that little space can be released this
> > way, and there may be some tricky locking issues.
>
> Sounds like this would be beneficial for environments with high
> update/delete transaction volumes, perhaps on smaller amounts of
> live/valid data.

But if dead pages are removed (returned to FSM?) as soon as last item is
removed from the page, the page usage will remain small. Or perhaps not?

That is, it's unlikely to collect large number of dead/free pages at the end
of the physical storage except if doing all this in single VACUUM session.

Daniel

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Kalchev 2003-02-13 08:23:58 Re: Brain dump: btree collapsing
Previous Message Daniel Kalchev 2003-02-13 08:10:31 Re: Brain dump: btree collapsing