Re: Postgres 9 : - How to interpret the EXPLAIN query results

From: Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com>
To: Khangelani Gama <kgama(at)argility(dot)com>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Postgres 9 : - How to interpret the EXPLAIN query results
Date: 2015-03-25 10:04:18
Message-ID: CA+h6AhjktYYyGW2dEDctE5jR=z_5r=NKjrAF=XaSWZ6sosZaEw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Wed, Mar 25, 2015 at 1:30 PM, Khangelani Gama <kgama(at)argility(dot)com> wrote:

> Hi
>
>
>
> Please help, how can I interpret the following results of my EXPLAIN query
> ?, I can see that the query will through 18586018 rows, but what’s the
> meaning of cost and width?
>

>
GroupAggregate (cost=762381141.96..768375132.77 rows=18586018 width=32)
>
>
​Its like ..

​NodeType (cost=startup-cost..total-cost rows=plan rows width=bytes per-row)

Documentation has briefed well on the explain output. Here's example.

postgres=# explain select * from foo;
QUERY PLAN
-----------------------------------------------------------
Seq Scan on foo (cost=0.00..5770.01 rows=400001 width=4)
(1 row)

postgres=# EXPLAIN (FORMAT JSON) SELECT * FROM foo;
QUERY PLAN
--------------------------------
[ +
{ +
"Plan": { +
"Node Type": "Seq Scan",+
"Relation Name": "foo", +
"Alias": "foo", +
"Startup Cost": 0.00, +
"Total Cost": 5770.01, +
"Plan Rows": 400001, +
"Plan Width": 4 +
} +
} +
]
(1 row)

http://www.postgresql.org/docs/9.3/static/sql-explain.html

---
Regards,
Raghavendra
EnterpriseDB Corporation
Blog: http://raghavt.blogspot.com/​

>
>
>
>
>
>
>
>
> CONFIDENTIALITY NOTICE
> The contents of and attachments to this e-mail are intended for the addressee only, and may contain the confidential
> information of Argility (Proprietary) Limited and/or its subsidiaries. Any review, use or dissemination thereof by anyone
> other than the intended addressee is prohibited.If you are not the intended addressee please notify the writer immediately
> and destroy the e-mail. Argility (Proprietary) Limited and its subsidiaries distance themselves from and accept no liability
> for unauthorised use of their e-mail facilities or e-mails sent other than strictly for business purposes.
>
>
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Paul Dunkler 2015-03-25 10:10:24 Re: pg_xlog-files not deleted on a standby after accidental server crash
Previous Message Anthony Nowocien 2015-03-25 09:33:17 Re: Postgres 9 : - How to interpret the EXPLAIN query results