pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Khangelani Gama <kgama@argility.com>
To: Thomas Kellerer <spam_eater@gmx.net>
To: pgsql-admin@postgresql.org
Subject: Re: Postgres 9 : - How to interpret the EXPLAIN query results
Date: Wed, 25 Mar 2015 13:34:35 +0200
Message-ID: <d3ca3e6d174a3cd29f0365e3e29dfb07@mail.gmail.com> (raw)
In-Reply-To: <meu4pq$eep$1@ger.gmane.org>
References: <a5cf86e816f64005722ba22e878b3c44@mail.gmail.com>
	<CA+h6AhjktYYyGW2dEDctE5jR=z_5r=NKjrAF=XaSWZ6sosZaEw@mail.gmail.com>
	<80b319b3f6696a7f1672a4640f55e803@mail.gmail.com>
	<meu4pq$eep$1@ger.gmane.org>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Thomas Kellerer
Sent: 25 March 2015 01:05 PM
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Postgres 9 : - How to interpret the EXPLAIN query
results

Khangelani Gama schrieb am 25.03.2015 um 11:28:
> Thanks  to all, but if this total cost is the total time it will take to
> retrieve the output then is it in minutes or milliseconds?
> If it’s in milliseconds does it mean that it take about 213 hrs for a
> total of 768375132.77

No. The cost is not the total time.

Quote from the manual

  measured in cost units that are arbitrary, but conventionally mean disk
page fetches

In general you can _assume_ that a query with a higher cost is likely to run
longer than an equivalent query with lower costs.

If you want the runtime of each step you need to use "explain (analyze)" -
again this is documented in the manual.

Thomas



Many Thanks Thomas




--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make
changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin


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.



-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (8+ messages)  latest in thread

Message-ID: <d3ca3e6d174a3cd29f0365e3e29dfb07@mail.gmail.com>
Permalink:  ../d3ca3e6d174a3cd29f0365e3e29dfb07@mail.gmail.com/
Also on:    postgresql.org/message-id/d3ca3e6d174a3cd29f0365e3e29dfb07@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: kgama@argility.com, spam_eater@gmx.net
  Subject: Re: Postgres 9 : - How to interpret the EXPLAIN query results
  In-Reply-To: <d3ca3e6d174a3cd29f0365e3e29dfb07@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox