Comment 2 for bug 1703658

I just started working on converting from GIST to GIN on a test database server.

I'm unclear on Kathy's statement that this requires a reingest. I don't see how it does, since the upgrade code is to drop the GIST index and create the GIN index. If someone knows why this would require a reingest, please comment on this bug.

NB: By "reingest," I assume anything that would require running the database functions used by the pingest.pl support script.

This also appears to be something that we could not do in our typical DB upgrade scripts. It would be good to include a small Perl utility to either write out the code to drop and create the indexes or to do the "conversion" itself. In my test case, I dumped the schemaname and indexdef from pg_indexes for the GIST indexes, and then used a regexp search and replace to get the SQL needed to drop the old and create the new indexes.