| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Thomas Hallgren <thomas(at)tada(dot)se> |
| Cc: | Richard Huxton <dev(at)archonet(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp>, Akshat Nair <akshat(dot)nair(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Get explain output of postgresql in Tables |
| Date: | 2006-04-12 15:29:53 |
| Message-ID: | 20060412152952.GF49405@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 12, 2006 at 04:53:20PM +0200, Thomas Hallgren wrote:
> <NestedLoop cost="1.06..40.43" rows="5" width="244">
> <JoinFilter publicTenk1Unique2="int4_tbl.f1">
> <HashAggregate cost="1.06..1.11" rows="5" width="4"/>
> </JoinFilter>
> </NestedLoop>
Well, the downside is that such a format means explain output is now
twice as long. But I'd love to see something like that as an option. I'd
also still like to see an SQL-parseable version as well, since I think
there's applications for that.
As for those who can't manage to post EXPLAIN ANALYZE to the list; as
long as ANALYZE isn't the default I don't see how making a less
human-readable version the default will solve anything, because we'll
still perpetually be asking people for the output of EXPLAIN ANALYZE. If
we want to increase the number of people who provide useful information
in initial performance questions, the answer is to make the information
about what to submit more prominent.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2006-04-12 15:43:27 | Re: Get explain output of postgresql in Tables |
| Previous Message | Thomas Hallgren | 2006-04-12 14:53:20 | Re: Get explain output of postgresql in Tables |