On Tue, 2008-10-07 at 08:14 -0700, Jeff Davis wrote:
> In the VACUUM VERBOSE output I included, you can see that the heap is
> only 785 pages (after 200M rows went through that table), and it
> maintains that consistently. That means to me that the VACUUMs are
> running and properly freeing the spa
On Tue, 2008-10-07 at 11:04 +0300, Heikki Linnakangas wrote:
> Jeff Davis wrote:
> > I see this problem on 8.3.3 now, too. Originally, I suppose my test was
> > not long enough, but now I see the problem after about 10 minutes of
> > running.
>
> I ran the script for about 30 minutes on CVS HEAD,
Jeff Davis wrote:
I see this problem on 8.3.3 now, too. Originally, I suppose my test was
not long enough, but now I see the problem after about 10 minutes of
running.
I ran the script for about 30 minutes on CVS HEAD, and the index didn't
grow at all after the first three iterations. Are you
On Mon, 2008-10-06 at 11:10 +0300, Heikki Linnakangas wrote:
> Jeff Davis wrote:
> > I am seeing index bloat in the current head when the indexed values are
> > constantly increasing, and the lower values are being constantly
> > deleted.
> >
> > ...
> > It's possible that this has something to do
Jeff Davis wrote:
I am seeing index bloat in the current head when the indexed values are
constantly increasing, and the lower values are being constantly
deleted.
...
It's possible that this has something to do with the new FSM.
Yep, it clearly has. Looks like I forgot about the index FSMs wh
I am seeing index bloat in the current head when the indexed values are
constantly increasing, and the lower values are being constantly
deleted.
I attached a simple python script that can be fed into psql. If this is
done on 8.3.3, the number of index relpages stays fairly constant,
around 500, a
