Re: Thoughts on maintaining 7.3

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Thoughts on maintaining 7.3
Date: 2003-10-09 19:34:27
Message-ID: 200310091934.h99JYR829125@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
> > The reason I'm waffling about whether the problem is completely fixed or
> > not is that the existing code will only remove-and-recycle completely
> > empty btree pages. As long as you have one key left on a page it will
> > stay there. So you could end up with ridiculously low percentage-filled
> > situations. This could be fixed by collapsing together adjacent
> > more-than-half-empty pages, but we ran into a lot of problems trying to
> > do that in a concurrent fashion. So I'm waiting to find out if real
> > usage patterns have a significant issue with this or not.
>
> If we have an exclusive lock during VACUUM FULL, should we just collapse
> the pages rather than REINDEX? I realize we might have lots of expired
> index tuples because VACUUM FULL creates new ones as part of
> reorganizing the heap.

Never mind --- I remember now that we are going to use VACUUM for a few
updates, and VACUUM FULL for big updates.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-10-09 19:36:12 Re: Thoughts on maintaining 7.3
Previous Message Bruce Momjian 2003-10-09 19:30:18 Re: Thoughts on maintaining 7.3