Skip to navigation
Watch our latest webinar on demand: Optimizing Postgres with Claude Code and the pganalyze MCP Server.
pganalyze
  • Docs
  • Our Key Features
    Query AdvisorDetect and fix Postgres query plan problemsIndex AdvisorFaster queries, less guessworkVACUUM AdvisorOptimize bloat, freezing and VACUUM performanceWorkbooksDedicated environment for query optimization
    All features
  • Fix Slow QueriesEnterprise Scale
  • Pricing
  • Blog
  • WebinarseBooksToolsCustomer StoriesBlogNewsletter
  • About usCareers
  • Contact
LoginFree Trial
pganalyze
Docs
Query AdvisorDetect and fix Postgres query plan problemsIndex AdvisorFaster queries, less guessworkVACUUM AdvisorOptimize bloat, freezing and VACUUM performanceWorkbooksDedicated environment for query optimization
See all features
Fix Slow QueriesEnterprise Scale
PricingBlog
WebinarseBooksToolsCustomer StoriesBlogNewsletter
About usCareers
Contact
Free TrialLog in
    • Overview
    • Installation Guide
    • pganalyze Collector
    • Query Performance
    • Query Advisor
    • EXPLAIN Plans
      • Overview
      • The Basics of Postgres Query Planning
      • EXPLAIN Grid view
      • Comparing EXPLAIN plans
      • Insights
      • Scan nodes
        • Sequential Scan
        • Index Scan
        • Index-Only Scan
        • Bitmap Heap Scan
        • Bitmap Index Scan
        • CTE Scan
        • Custom Scan
        • Foreign Scan
        • Function Scan
        • Subquery Scan
        • Table Sample Scan
        • Tid Scan
        • Values Scan
        • Work Table Scan
      • Join nodes
      • Other nodes
    • Workbooks
    • Index Advisor
    • Indexing Engine
    • VACUUM Advisor
    • Schema Statistics
    • Log Insights
    • Connections
    • Alerts & Check-Up
    • Account Management
    • MCP Server (Preview)
    • OpenTelemetry Integration
    • pganalyze Enterprise Server
    • pganalyze GraphQL API
    • Open-Source Components
❮ Documentation: EXPLAIN - Scan Nodes

EXPLAIN - Subquery Scan

Description:

A Subquery Scan is for scanning the output of a sub-query in the range table. We often need an extra plan node above the sub-query’s plan to perform expression evaluations (which we can’t push into the sub-query without risking changing its semantics).

Important Fields:

  • Filter
  • Rows Removed by Filter

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

Logo
  • Contact
  • Plans & Pricing
  • Resources
  • Enterprise
  • Documentation
  • Customer Stories
  • Careers
  • Index Advisor
  • Security
  • Status
  • Postgres Query Formatter
  • Compare pganalyze
  • Terms of Service
  • Privacy Policy
  • Newsletter
  • SOC 2 Type 2
  • Do Not Sell My Personal Information

Get in touch

Use the contact us form or email sales:
 sales@pganalyze.com

SOC 2 certification

pganalyze is SOC 2 Type 2 certified

pganalyze is SOC 2 Type 2 certified
© 2026 Duboce Labs, Inc.