Re: Disabling an index temporarily - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Disabling an index temporarily
Date
Msg-id 22413.1450065802@sss.pgh.pa.us
Whole thread Raw
In response to Re: Disabling an index temporarily  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: Disabling an index temporarily  (Corey Huinker <corey.huinker@gmail.com>)
List pgsql-hackers
Jeff Janes <jeff.janes@gmail.com> writes:
> Not to hijack the thread even further in the wrong direction, but I
> think what Corey really wants here is to stop maintaining the index at
> retail while preserving the existing definition and existing index
> data, and then to do a wholesale fix-up, like what is done in the 2nd
> half of a create index concurrently, upon re-enabling it.

Meh.  Why not just drop the index?  I mean, yeah, you might save a few
keystrokes when and if you ever re-enable it, but this sure seems like
a feature in search of a use-case.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Disabling an index temporarily
Next
From: Michael Paquier
Date:
Subject: Re: Making tab-complete.c easier to maintain