4 ms·
I believe HOT provided some of the advantages of covering indexes. Covering indexes is tricky in Postgres, due to its MVCC implementation. Versioning info is i
by geophile 8y ago
I believe HOT provided some of the advantages of covering indexes.
Covering indexes is tricky in Postgres, due to its MVCC implementation. Versioning info is in the table, not the index, so the index may have stale data. The table itself has to be consulted to find out if the data in the index is actually visible to your transaction.
- petergeoghegan 8y agoYou're talking about index-only scans. Those appeared in Postgres 9.2, which came out about 5 years ago. INCLUDE/covering indexes are indexes that can include extra "payload" columns, and exist only for the benefit of index-only scans. You can add something extra to the primary key for the largest table in your database, all without changing how and when duplicate violation errors are raised.