Re: Marking indexes out of date (WAS: loading data, creating indexes, clustering, vacuum) feature request?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
Cc: Glen Parker <glenebob(at)nwlink(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Marking indexes out of date (WAS: loading data, creating indexes, clustering, vacuum) feature request?
Date: 2006-12-08 23:59:54
Message-ID: 25252.1165622394@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> One issue would be that even disabled indexes would need to be updated
> when there are new rows. If you don't update the index when it's
> disabled, then re-enabling will essentially need to rebuild the index.

I assume that's what he wants. However, it's not immediately clear that
there's a sufficient use case for this to justify the extra apparatus
compared to just DROP INDEX (and recreate it later).

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message sasan3@gmail.com 2006-12-09 01:56:22 Re: can this be done in one SQL selcet statement?!
Previous Message Jeff Davis 2006-12-08 23:49:42 Re: Performance figures from DbMail list