Re: Postgresql concern of effect of invalid index

Matheus de Oliveira <matioli.matheus@gmail.com> wrote:=0A> Burgess, Freddie=
 <FBurgess@radiantblue.com> wrote:=0A>=0A>> My question is? What are the ra=
mifications of having this=0A>> spatial indexes remain in this state?=0A=0A=
>> update pg_index set indisvalid =3D false=0A>>=A0=A0 where indexrelid =3D=
 'sidx_sponser_report_y2014m06'::regclass;=0A>=0A> If you marked it as inva=
lid, then it is not going to be updated=0A> anymore.=0A=0AI think you are c=
onfusing indisvalid with indisready:=0A=0Ahttp://www.postgresql.org/docs/cu=
rrent/interactive/catalog-pg-index.html=0A=0AFlagging it is invalid should =
suppress its use for queries, yet=0Astill do all the work of maintaining it=
.=0A=0A> BTW, you'd better take this to -performance list and discuss=0A> a=
bout why it is choosing a *bad* index instead of messing with=0A> the catal=
og.=0A=0A+1=0A=0AIn any event, this is most definitely *not* a bug report, =
so it=0Abelongs on a different list.=0A=0A--=0AKevin Grittner=0AEDB: http:/=
/www.enterprisedb.com=0AThe Enterprise PostgreSQL Company