Re: Invisible Indexes - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Invisible Indexes
Date
Msg-id 3cbca94b-1e63-cf82-56d8-42b4a11219be@2ndQuadrant.com
Whole thread Raw
In response to Re: Invisible Indexes  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers

On 06/18/2018 05:44 PM, Peter Geoghegan wrote:
> On Mon, Jun 18, 2018 at 2:36 PM, Andrew Dunstan
> <andrew.dunstan@2ndquadrant.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.


Well, that's encouraging ;-)

> Haven't thought
> about the syntax, though.
>



I envisioned:

CREATE INDEX .... [NOT VISIBLE] ...;
ALTER INDEX ... [SET [NOT] VISIBLE] ...;


Let the bikeshedding begin :-)

cheers

andrew

-- 
Andrew Dunstan                https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Invisible Indexes
Next
From: Peter Geoghegan
Date:
Subject: Re: [WIP] [B-Tree] Retail IndexTuple deletion