Re: GiST insert algorithm rewrite - Mailing list pgsql-hackers

From Robert Haas
Subject Re: GiST insert algorithm rewrite
Date
Msg-id AANLkTinF49MPofHsUL-vFZ828=a8dv9hb-oFN1rDCRwy@mail.gmail.com
Whole thread Raw
In response to Re: GiST insert algorithm rewrite  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Nov 16, 2010 at 3:46 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> Oh.  So do the indexes just degrade over time until they eventually
>> need to be REINDEX'd?
>
> At some point you might reach a state where a reindex would be helpful.
> But the same is true of btrees.  I don't think this is a serious
> objection, at least not unless backed by evidence that the tree often
> degrades rapidly.  Anyway fixing it would be material for a different
> patch.

Oh, I agree it's not for this patch to fix it, if it's already that
way.  I was just curious.  I think index maintenance is going to be a
problem we have to devote some cycles to down the road, though.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: GiST insert algorithm rewrite
Next
From: Peter Eisentraut
Date:
Subject: Re: Per-column collation