Postgresql concern of effect of invalid index

Logged by: Freddie Burgess
Email address: fburgess(at)radiantblue(dot)com
PostgreSQL version: 9.3.4
Operating system: Red_hat Linux 6.4
Description:

We purposely set the "indisvalid" flag to false to force the planner to choose one of the other indexes which executes more efficiently, we want to drop the spatial index altogether, but because this partition table holds 14 billion rows it would take a long time to recreate all of the spatial indexes, if one of our clients request an ad-hoc spatial query on historical data down the road.

My question is? What are the ramifications of having this spatial indexes remain in this state?

thanks

update pg_index set indisvalid = false where indexrelid = 'sidx_sponser_report_y2014m06'::regclass;

Indexes:
"rpi_sponser_report_y2014m06_pkey" PRIMARY KEY, btree (sponser_report_uid), tablespace "sponser_data_y2014"
"idx_sessiondatetime_rpi_sponser_report_y2014m06" btree (session_uid, origin_date_time), tablespace "sponser_data_y2014"
"idx_uuid_rpi_sponser_report_y2014m06" btree (sponser_report_uuid), tablespace "sponser_data_y2014"
"sidx_sponser_report_y2014m06" gist (sponser_location) INVALID, tablespace "sponser_data_y2014"