การสร้างดัชนีใหม่และการดูแลดัชนี

Indexes are vital for database performance, but like any component, they need maintenance. Over time, indexes can become less efficient due to fragmentation and 'bloat'.

In this lesson, we'll learn why index maintenance is crucial, how to spot issues like bloat, and how to fix them using reindexing.

Index bloat refers to wasted space within an index. It occurs when index entries become outdated but are not immediately removed, or when an index structure becomes inefficient.

This 'bloat' can lead to:

• Larger index files, consuming more disk space.
• More I/O operations, slowing down queries.
• Reduced cache effectiveness.

PostgreSQL uses a technique called MVCC (Multi-Version Concurrency Control). When you UPDATE or DELETE rows, the old versions (called 'dead tuples') aren't immediately removed from the table or its indexes.

The VACUUM process cleans up these dead tuples. However, if VACUUM doesn't run frequently enough, or if transactions hold locks preventing cleanup, dead tuples accumulate, leading to bloat.

Spotting bloat can be tricky. You can't just look at file size, as it includes useful data. However, you can query PostgreSQL's system catalogs to estimate bloat by comparing the actual space used by an index to the space it should theoretically occupy.

Key tables for this are pg_class (for relation sizes) and pg_stat_user_indexes (for usage statistics).

While a full bloat calculation is complex, you can easily check an index's current size. A rapidly growing index size without corresponding data growth might signal bloat. Replace 'your_index_name' with an actual index.

Reindexing is the process of rebuilding an index from scratch. When you reindex, PostgreSQL constructs a completely new, clean version of the index.

This new index is:

• Free of bloat and fragmentation.
• Optimized for storage and access.
• Potentially faster for queries.

Reindexing isn't a daily task, but it's important for several situations:

• High Index Bloat: When bloat significantly increases index size and degrades performance.
• Performance Degradation: If query plans show indexes are less effective over time.
• Schema Changes: After major changes that might affect index structure.
• PostgreSQL Upgrades: Sometimes recommended for optimal performance with new versions.

PostgreSQL provides the REINDEX command to rebuild indexes. You can reindex individual indexes, all indexes on a table, or even all indexes in a database.

The CONCURRENTLY option is crucial for production systems as it allows reindexing without blocking reads or writes on the table. Without it, the table is locked during the operation.

To reindex a specific index, use the REINDEX INDEX command. Remember to use CONCURRENTLY for non-blocking operations in production. Replace 'my_table_col_idx' with your actual index name.

You can also reindex all indexes associated with a particular table using REINDEX TABLE. This is convenient but affects all indexes on that table. Again, CONCURRENTLY is highly recommended.

Which of the following is a primary reason to use REINDEX ... CONCURRENTLY in a production PostgreSQL environment?

Congratulations! You've learned about the critical aspects of PostgreSQL index maintenance.

• You can now identify index bloat and understand how it impacts performance.
• You know when and why to perform reindexing.
• You've seen how to use the REINDEX command, especially with the important CONCURRENTLY option.

Regular monitoring and maintenance of your indexes will keep your PostgreSQL database running smoothly and efficiently!