Re: Automatic free space map filling

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Zeugswetter Andreas DCP SD <ZeugswetterA(at)spardat(dot)at>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Csaba Nagy <nagy(at)ecircle-ag(dot)com>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, Christopher Browne <cbbrowne(at)acm(dot)org>, postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Automatic free space map filling
Date: 2006-03-03 16:26:28
Message-ID: 200603031626.k23GQSX20380@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Zeugswetter Andreas DCP SD wrote:
>
> > > But what about index clearing? When do you scan each index?
> >
> > At the end of each iteration (or earlier, depending on
> > maintenance_work_mem). So for each iteration you would need
> > to scan the indexes.
> >
> > Maybe we could make maintenance_work_mem be the deciding
> > factor; after scanning the indexes, do the release/reacquire
> > locks cycle.
>
> But you could do the indexes first and remember how far you can
> vacuum the heap later.
>
> So you might as well do each index separately first and remember
> how far you can go with the heap for each one.
> Then do the heap with a special restriction that comes from what you
> remembered from the indexes.
> You can now separate the heap vacuum in arbitrarily large transactions,
> since the indexes are already taken care of.
>
> (You only vacuum to the point of the eldest vacuumed index)

I thought you need to know the heap tids to remove from the index, so
how do you do the index first?

--
Bruce Momjian http://candle.pha.pa.us
SRA OSS, Inc. http://www.sraoss.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-03-03 16:37:00 Re: Automatic free space map filling
Previous Message Zeugswetter Andreas DCP SD 2006-03-03 16:20:29 Re: Automatic free space map filling