Pg_stat_user_indexes on Postgres Scripts

Find PostgreSQL Index Bloat and Wasted Space

Tue, 31 Mar 2026 00:00:00 +0000

How to Find Index Bloat and Wasted Space in PostgreSQL

Just like tables, PostgreSQL indexes can become bloated over time. When rows are updated or deleted, the old index entries are not removed immediately. They stay in the index as dead entries, wasting space and slowing down index scans.

B-tree indexes are the most common type in PostgreSQL and the most prone to bloat. This query estimates how much space is wasted in each B-tree index, so you can decide which ones need to be rebuilt.

PostgreSQL Statistics Settings Query Guide

Tue, 17 Mar 2026 00:00:00 +0000

PostgreSQL Statistics Settings Query Guide

This PostgreSQL query retrieves all statistics collection configuration settings from the pg_settings system view. These parameters control what runtime data PostgreSQL collects about query execution, table activity, and performance, feeding into the pg_stat_* monitoring views.

Purpose and Overview

PostgreSQL's statistics collector gathers data about database activity and makes it available through system views like pg_stat_activity, pg_stat_user_tables, and pg_stat_statements. If the underlying collection settings are disabled, those views return incomplete or empty data.

List PostgreSQL Tables by Size with SQL

Sun, 15 Mar 2026 00:00:00 +0000

List PostgreSQL Tables by Size with SQL

This PostgreSQL query lists all tables in the current database sorted by their total size, largest first. It uses pg_total_relation_size() to include the table data, indexes, TOAST storage, and free space map in the size calculation.

Purpose and Overview

Disk space pressure is a common operational concern in any growing database. Knowing which tables consume the most space allows administrators to prioritise archiving, partitioning, or compression efforts. It also helps explain sudden disk growth when a particular table has expanded unexpectedly.

How to Monitor PostgreSQL Index Cache for High Speed Queries

Mon, 18 Mar 2024 00:00:00 +0000

Keeping PostgreSQL Queries Speeding Along: Monitoring Index Cache Hit Rates

For a smooth-running PostgreSQL database, ensuring efficient access to frequently used data is crucial. Indexes act as shortcuts, speeding up queries. But how well are those indexes utilized? This post explores a SQL query that helps you monitor the PostgreSQL index cache hit rate, offering valuable insights into your database's performance.

Sample Code

1SELECT sum(idx_blks_read) as idx_read,
2 sum(idx_blks_hit) as idx_hit,
3 (sum(idx_blks_hit) - sum(idx_blks_read)) / sum(idx_blks_hit) as ratio
4FROM pg_statio_user_indexes;

Understanding the Code:

Monitor PostgreSQL Index Usage for Speedy Queries

Sun, 17 Mar 2024 00:00:00 +0000

Monitoring PostgreSQL Index Usage: Keeping Your Queries Speedy

In the fast-paced world of web applications, ensuring efficient database queries is paramount. PostgreSQL's powerful indexing capabilities play a crucial role in achieving optimal performance. This post delves into a SQL query that helps you monitor index usage rates and identify areas for potential optimization.

The Table Index Usage Rates Should not be less than 0.99