| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Invisible Indexes |
| Date: | 2018-06-18 22:04:18 |
| Message-ID: | CAH2-WzkpMkF2Kt6ZoNgThA+1XaQf==n5cv7GDZVNAyrwrc=_VA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 18, 2018 at 2:57 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Admittedly, this isn't great in a production environment, but neither
> would be disabling the index in the way you suggest.
>
> I think the actually desirable way to handle this sort of thing is through
> an "index advisor" sort of plugin, which can hide a given index from the
> planner without any globally visible side-effects.
The globally visible side-effects are the point, though. Some users
desire cheap insurance against dropping what turns out to be the wrong
index.
FWIW, this isn't just a MySQL feature. Oracle has a similar feature.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-06-18 22:05:11 | Re: Invisible Indexes |
| Previous Message | Andres Freund | 2018-06-18 22:00:33 | Re: Invisible Indexes |