EXPLAIN - Insights: I/O Heavy


Postgres will often spend most of its I/O time on a query in a small set of plan nodes. This insight identifies the most expensive nodes (according to time spent doing I/O) to guide optimization. Since I/O is usually the bottleneck in many database queries, focusing on nodes performing the bulk of I/O is a good rule of thumb.

This insight requires track_io_timing to be enabled on the database.

Recommended Action:

If possible, reduce the amount of I/O performed in this node. There are many possible causes of excessive I/O, but several are identified by other insights, like Inefficient Index or Large Offset.

Couldn't find what you were looking for or want to talk about something specific?
Start a conversation with us →