Re: Free space mapping (was Re: Multi-Versions and Vacuum)

From: Mark Kirkwood <markir(at)slingshot(dot)co(dot)nz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgman(at)candle(dot)pha(dot)pa(dot)us, pgsql-general(at)postgresql(dot)org, andrew(at)libertyrms(dot)info
Subject: Re: Free space mapping (was Re: Multi-Versions and Vacuum)
Date: 2002-08-27 23:10:44
Message-ID: 3D6C06F4.8040201@slingshot.co.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:

>It doesn't need a lot of examination in my mind: the cause is surely
>growth of the index on the toast table. Since that index's first column
>is the OID assigned to the toast item, the range of indexed values tends
>to shift over time, causing the leftmost parts of the index btree to
>become sparsely populated and eventually empty. Since we don't
>currently have code to collapse out empty pages in a btree, the index
>grows during continued update activity, even if the total amount of data
>you're storing isn't growing. This is quite unrelated to the free space
>map --- indexes don't use the FSM.
>
>
>
hmmm, good point - I thought the toast table was growing too, but I will
check this.

regards

Mark

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2002-08-27 23:19:46 Re: Free space mapping (was Re: Multi-Versions and Vacuum)
Previous Message Tom Lane 2002-08-27 22:45:05 Re: Free space mapping (was Re: Multi-Versions and Vacuum)