Re: Subject: bool / vacuum full bug followup part 2 - Mailing list pgsql-general

From Tom Lane
Subject Re: Subject: bool / vacuum full bug followup part 2
Date
Msg-id 19070.1020549998@sss.pgh.pa.us
Whole thread Raw
In response to Re: Subject: bool / vacuum full bug followup part 2  (Jeffrey Baker <jwbaker@acm.org>)
Responses Re: Subject: bool / vacuum full bug followup part 2
List pgsql-general
Jeffrey Baker <jwbaker@acm.org> writes:
> On Fri, May 03, 2002 at 03:47:54PM -0400, Tom Lane wrote:
>> AFAIK there's not a big problem with index growth if the range of index
>> keys remains reasonably static.  The problem comes in if you have a
>> range of values that keeps growing (eg, you are indexing a SERIAL or
>> timestamp column).  The right end of the btree keeps growing, but
>> there's no mechanism to collapse out no-longer-used space at the left
>> end.

> Wouldn't that explain the complaints I have about my toast tables
> always growing?

It'd explain the indexes growing --- the index key is an OID, which will
keep increasing as you store new toasted values.  I thought you'd been
complaining about the tables themselves, though.

            regards, tom lane

pgsql-general by date:

Previous
From: Ron Snyder
Date:
Subject: Re: Using views and MS access via odbc
Next
From: Jeffrey Baker
Date:
Subject: Re: Subject: bool / vacuum full bug followup part 2