Database Research & Development

  • Home
  • NoSQL
    • NoSQL
    • Cassandra
  • Databases
    • Database Theory
    • Database Designing
    • SQL Server Coding Standards
    • SQL Server
    • PostgreSQL
    • MySQL
    • Greenplum
    • Linux
  • Interviews
    • SQL Server Interviews
    • MySQL Interviews
    • SQL Puzzles
  • DBA Scripts
    • SQL Server DBA Scripts
    • PostgreSQL DBA Scripts
    • MySQL DBA Scripts
    • Greenplum DBA Scripts
  • Home
  • Blog Archives !
  • (: Laugh@dbrnd :)
  • Contact Me !
sqlserverinterviews
Home 2016 September PostgreSQL: Using EXPLAIN ANALYZE, Know your Query Execution Plan

PostgreSQL: Using EXPLAIN ANALYZE, Know your Query Execution Plan

This article is half-done without your Comment! *** Please share your thoughts via Comment ***

Like any other RDBMS, PostgreSQL generates a Query Execution Plan for each query that it receives.

It is also used Genetic Query Optimizer (GEQO) that does query planning for heuristic search and It reduce query planning time for large and complex queries.

An Optimizer always tries to choose a good Query Execution Plan.

The structure of Query Execution Plan is like a Tree and It contains different information like: type of scan details, join details, sorting details, aggregation details, Estimated rows details, Estimated start-up cost, Estimated total cost and others.

To know about the Query Execution Plan, is very important for all Database Professionals because It helps us to improve the Query Performance.

With the help of Query Execution Plan, We can make our decisions on Index tuning, Join tuning and other.

In PostgreSQL, we have EXPLAIN and EXPLAIN ANALYZE command to know about the Query Execution Plan.

Here, I have used one table tbl_itemtransactions which you can create using below post.

Example of EXPLAIN: It generates the Estimated Query Execution Plan with out executing an actual SQL Query.

1
2
3
4
5
6
7
8
EXPLAIN SELECT COUNT(1) FROM tbl_itemtransactions;
 
/*
Result:
"Aggregate (cost=2555525.00..2555525.01 rows=1 width=0)"
" -> Seq Scan on tbl_itemtransactions
(cost=0.00..2216945.00 rows=135432000 width=0)"
*/

Example of EXPLAIN ANALYZE: It first executes the SQL Query and than It generates the actual Query Execution Plan.

1
2
3
4
5
6
7
8
9
10
11
12
EXPLAIN ANALYZE SELECT COUNT(1) FROM tbl_itemtransactions;
 
/*
Result:
"Aggregate (cost=2555525.00..2555525.01 rows=1 width=0)
(actual time=52660.132..52660.133 rows=1 loops=1)"
" -> Seq Scan on tbl_itemtransactions
(cost=0.00..2216945.00 rows=135432000 width=0)
(actual time=0.027..46193.484 rows=135432001 loops=1)"
"Planning time: 0.204 ms"
"Execution time: 52660.237 ms"
*/

Sep 8, 2016Anvesh Patel
PostgreSQL 9.1 is going to Shutdown, no more Support and Release UpdatePostgreSQL: Track ALL SQL Query Execution Statistics using pg_stat_statements Extension (Day 1/2)
Anvesh Patel
Anvesh Patel

Database Engineer

September 8, 2016 PostgreSQLAnvesh Patel, database, database research and development, dbrnd, Execution Plan, EXPLAIN, Explain Analyze, Genetic Query Optimizer, GEQO, plpgsql, Postgres Query, postgresql, PostgreSQL Administrator, PostgreSQL Error, PostgreSQL Programming, PostgreSQL Tips and Tricks, Query Optimizer, Query Plan
About Me!

I'm Anvesh Patel, a Database Engineer certified by Oracle and IBM. I'm working as a Database Architect, Database Optimizer, Database Administrator, Database Developer. Providing the best articles and solutions for different problems in the best manner through my blogs is my passion. I have more than six years of experience with various RDBMS products like MSSQL Server, PostgreSQL, MySQL, Greenplum and currently learning and doing research on BIGData and NoSQL technology. -- Hyderabad, India.

About DBRND !

dbrnd

This is a personal blog (www.dbrnd.com).

Any views or opinions represented in this blog are personal and belong solely to the blog owner and do not represent those of people, institutions or organizations that the owner may or may not be associated with in professional or personal capacity, unless explicitly stated.

Feel free to challenge me, disagree with me, or tell me I’m completely nuts in the comments section of each blog entry, but I reserve the right to delete any comment for any reason whatsoever (abusive, profane, rude, or anonymous comments) - so keep it polite.

The content of this website is protected by copyright. No portion of this website may be copied or replicated in any form without the written consent of the website owner.

Recent Comments !
  • Anvesh Patel { Sure will do... } – May 27, 12:43 PM
  • Anvesh Patel { Great... } – May 27, 12:41 PM
  • Anvesh Patel { Great... } – May 27, 12:39 PM
  • Anvesh Patel { Great... } – May 27, 12:36 PM
  • Anvesh Patel { Great... } – May 27, 12:28 PM
  • Anvesh Patel { Great... } – May 27, 12:27 PM
  • Anvesh Patel { Great... } – May 27, 12:16 PM
  • Older »
Follow Me !
  • facebook
  • linkedin
  • twitter
  • youtube
  • google
  • flickr
© 2015 – 2019 All rights reserved. Database Research & Development (dbrnd.com)
Posting....