We just released a new major feature on pganalyze: Automated EXPLAIN plan analysis and plan visualization.Learn more

EXPLAIN - Insights: Slow Scan

Description:

A sequential scan is a simple way to fetch data from a table, but unless you need a large fraction of the table data, it’s rarely the most efficient. When a sequential scan in an EXPLAIN plan shows a large Rows Removed by Filter, this suggests it may be more efficient to fetch this data using an index.

Recommended Action:

Create an index (possibly a partial index, an expression index, or using a specific index type) so a more efficient scan can be used instead. If indexes exist but are not being used, they may not be suitable for this query.


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