| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> |
| Subject: | Re: GiST insert algorithm rewrite |
| Date: | 2010-11-16 20:53:44 |
| Message-ID: | AANLkTinF49MPofHsUL-vFZ828=a8dv9hb-oFN1rDCRwy@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 16, 2010 at 3:46 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2010-11-16 20:56:04 | Re: Per-column collation |
| Previous Message | Heikki Linnakangas | 2010-11-16 20:51:00 | Re: GiST insert algorithm rewrite |