| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Markus Bertheau" <mbertheau(dot)pg(at)googlemail(dot)com> |
| Cc: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Peter Koczan" <pjkoczan(at)gmail(dot)com>, pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: disabling an index without deleting it? |
| Date: | 2008-02-27 05:38:49 |
| Message-ID: | 14265.1204090729@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
"Markus Bertheau" <mbertheau(dot)pg(at)googlemail(dot)com> writes:
> On the other hand, if the only reason to have that feature is to plan
> and execute queries pretending that one index doesn't exist, then DROP
> INDEX DEFERRED is not the most straightforward syntax.
Yeah, I was just about to mention that 8.3 has a hook that allows a
plug-in to manipulate the planner's notions of which indexes exist.
Ignoring a specific index would be really trivial.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James Mansion | 2008-02-27 06:00:05 | Re: LISTEN / NOTIFY performance in 8.3 |
| Previous Message | Markus Bertheau | 2008-02-27 05:29:55 | Re: disabling an index without deleting it? |