From: | Sim Zacks <sim(at)compulab(dot)co(dot)il> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | understanding explain data |
Date: | 2006-05-10 11:34:20 |
Message-ID: | e3sfnb$j42$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I am looking at the explain data for my query and it mostly
understandable thanks to an excellent article by Jim Nasby,
http://www.pervasive-postgres.com/instantkb13/article.aspx?id=10120
It is very time consuming and confusing walking through the explain. Is
there a possibility (or does it even make sense), to be able to feed the
explain into an application that would tell you what you need to do to
optimize the query?
Something such as: with this explain data, adding an index on table tbl
column A would drastically improve the efficiency. Or at least an
application that would say, the least efficient part of your query is on
this part of the code so that you could more easily figure out what to
do about it.
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2006-05-10 12:01:18 | Re: [GENERAL] intarray internals |
Previous Message | Nis Jorgensen | 2006-05-10 11:13:53 | Re: Exporting postgres query to CSV |