Re-index rebuilds an index using the data stored in the index's table, replacing the old copy of the index. There are several scenarios in which to use Re-index;

  • An index has become corrupted, and no longer contains valid data. Although in theory this should never happen, in practice indexes can become corrupted due to software bugs or hardware failures. Re-index provides a recovery method.
  • An index has become "bloated", that is it contains many empty or nearly-empty pages. This can occur with B-tree indexes in PostgreSQL under certain uncommon access patterns. re-index provides a way to reduce the space consumption of the index by writing a new version of the index without the dead pages.


The text index in Vidispine can be fully reindexed without disturbing production. The re-indexing process also handles application server restarts, and can be monitored. Normally, re-indexing is only needed if the metadata field definition is changed, but it can be a good idea to reindex if the database is moved or if upgrading to a newer version of Vidispine.


How to reindex items;

http://apidoc.vidispine.com/latest/ref/item/item.html?highlight=reindex#re-index-item


How to reindex metadata;

http://apidoc.vidispine.com/latest/ref/metadata/reindex.html#re-indexing-metadata