During index tinkering I save a snapshot of the index stats and/or run pg_stat_reset, make the change, and then monitor the new block rate of I/O to the indexes. The index block read stats show the new hot and dead spots. My WIP catalog query samples: github.com/CrunchyData/pg…

github.com

GitHub - CrunchyData/pg_goggles: pg_goggles provides better scaled and summarized views into...

pg_goggles provides better scaled and summarized views into PostgreSQL's cryptic internal counters. - CrunchyData/pg_goggles

Three things to remember about Postgres indexes: 1) Indexes can speed up operations for a query that SELECT * for a column but they can also make other query functions joins, sorting (ORDER BY) and grouping (GROUP BY) faster. 2) Creating an index on a column doesn't guarantee…



United States Trends
Loading...

Something went wrong.


Something went wrong.