On Mon, Dec 14, 2015 at 12:27 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Certainly, there's opportunities to improve the flexibility of the > index-disable specifications in the plug-in Oleg and Teodor did. But > I think that that is the right basic approach: some sort of SET command, > not anything that alters the catalogs. We already have lots of > infrastructure that could handle desires like having specific values > active in only some sessions.
ISTM that an intuitive answer is something like enable_indexscan_list = 'index1, index2' and not worry about any disable switch, that's more in line with the equivalent planner-level GUC. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
