select count(*) FROM items_2004_07_29 as items WHERE true AND index @@ to_tsquery('default', '( audiovox)') ;
aers=# reindex index idx_title_2004_07_29;
aers=# select count(*) FROM items_2004_07_29 as items WHERE true AND index @@ to_tsquery('default', '( audiovox)') ;
Here are 2 searches using a gist index, the first one has a gist index which is not properly created but does not though an error in creation. After doing a few searches I noticed the numbers were way off so I reindexed. The problem was fixed and the search works properly.
Is there a problem with indexing? Do you know of this problem?
Is there a way to fix it?
We are getting this error for other index's including primary key indexs where we get OID page not found errors and the index corruption as posted above.
Sometimes when the index is broken it will cause run away searches which eat up all the memory and the server needs to be restarted.
Anyways this all looks to be in index problem, vacuum/analyze does not fix it only reindexing does.