hard20 pts · first answer countsindexing
Index on a frequently updated column
A PostgreSQL sessions table updates last_seen_at on every request. After adding an index on last_seen_at, table bloat and write I/O jump sharply. What is the most likely cause?
Discussion 0
Join free to post in the discussion.
Related questions
- When a B-tree index helpsDatabase Administrator
- Index on a yes/no columnDatabase Administrator
- How InnoDB stores table rowsDatabase Administrator
- What an InnoDB secondary index points toDatabase Administrator
- LIKE with a leading %Database Administrator
- What a hash index supportsDatabase Administrator
- Cost of extra indexes on insertsDatabase Administrator
- EXPLAIN versus EXPLAIN ANALYZEDatabase Administrator