Re: Invisible Indexes

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Invisible Indexes
Date: 2018-06-18 21:44:29
Message-ID: CAH2-WzkeDCgRSYmE4eKZ92KDJk4CpK9x7B8e1c3774CmpAdGGg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 18, 2018 at 2:36 PM, Andrew Dunstan
<andrew(dot)dunstan(at)2ndquadrant(dot)com> wrote:
>
> This is a MySQL feature, where an index is not considered by the planner.
> Implementing it should be fairly straightforward, adding a new boolean to
> pg_index, and options to CREATE INDEX and ALTER INDEX. I guess VISIBLE would
> become a new unreserved keyword.

> So, do we want this feature? If we do I'll go ahead and prepare a patch.

I know that it's definitely a feature that I want. Haven't thought
about the syntax, though.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaime Casanova 2018-06-18 21:46:02 Re: Invisible Indexes
Previous Message Andrew Dunstan 2018-06-18 21:36:57 Invisible Indexes