--- title: Postgres Support Recap: Investigating Postgres Query... description: Three practical strategies for investigating Postgres query performance issues are outlined: using the pg_stat_statements extension to identify long-running... canonical: https://daily.dev/posts/postgres-support-recap-investigating-postgres-query-performance-a2iu6vqk1 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Postgres Support Recap: Investigating Postgres Query Performance | daily.dev og:description: Three practical strategies for investigating Postgres query performance issues are outlined: using the pg_stat_statements extension to identify long-running... og:url: https://daily.dev/posts/postgres-support-recap-investigating-postgres-query-performance-a2iu6vqk1 og:image: https://api.daily.dev/og/posts/a2IU6VQK1.png og:image:alt: Postgres Support Recap: Investigating Postgres Query Performance og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Postgres Support Recap: Investigating Postgres Query Performance **[Neon](https://daily.dev/sources/neontech)** · 8 min read · 0 upvotes · 0 comments ## Summary Three practical strategies for investigating Postgres query performance issues are outlined: using the pg_stat_statements extension to identify long-running queries, checking cache hit ratios (including Neon's local file cache via neon_stat_file_cache), and detecting and reducing table/index bloat via VACUUM and REINDEX. The post also introduces PgHero, a free open-source performance dashboard for Postgres that provides a visual alternative to running raw SQL diagnostics, with instructions for deploying it via Docker against a Neon database. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [Debug your Postgres from the terminal: a tour of \`neon inspect db\`](https://daily.dev/posts/debug-your-postgres-from-the-terminal-a-tour-of-neon-inspect-db--udxpnfh83) · Neon · 15 upvotes · 0 comments --- Tags: [#database](https://daily.dev/tags/database), [#postgresql](https://daily.dev/tags/postgresql) [View this post on daily.dev](https://daily.dev/posts/postgres-support-recap-investigating-postgres-query-performance-a2iu6vqk1) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Postgres Support Recap: Investigating Postgres Query Performance","url":"https://daily.dev/posts/postgres-support-recap-investigating-postgres-query-performance-a2iu6vqk1","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/postgres-support-recap-investigating-postgres-query-performance-a2iu6vqk1"},"datePublished":"2026-07-09T06:57:57.284Z","dateModified":"2026-07-09T07:02:53.103Z","description":"Three practical strategies for investigating Postgres query performance issues are outlined: using the pg_stat_statements extension to identify long-running...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7a56261a709fdde3a9b19171ef8d6e49?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7a56261a709fdde3a9b19171ef8d6e49?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Neon","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Neon","logo":"https://media.daily.dev/image/upload/s--65EDghou--/f_auto/v1724339118/logos/neontech","url":"https://daily.dev/sources/neontech"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/postgres-support-recap-investigating-postgres-query-performance-a2iu6vqk1","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"database,postgresql","timeRequired":"PT8M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Neon","item":"https://daily.dev/sources/neontech"},{"@type":"ListItem","position":3,"name":"Postgres Support Recap: Investigating Postgres Query Performance"}]} ```