From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 08:45:19 |
Message-ID: | 443CBE1F.2000609@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jim C. Nasby wrote:
> On Mon, Apr 10, 2006 at 10:44:15AM +0100, Richard Huxton wrote:
>> Bruce Momjian wrote:
>>> * Allow EXPLAIN output to be more easily processed by scripts
>> Can I request an extension/additional point?
>> * Design EXPLAIN output to survive cut & paste on mailing-lists
>>
>> Being able to paste into a web-form and get something readable formatted
>> back would be very useful on the lists. Sometimes it takes me longer to
>> reformat the explain than it does to understand the problem.
>
> Actually, I've been wondering about better ways to handle this. One
> thought is to come up with a non-human readable format that could easily
> be cut and pasted into a website that would then provide something easy
> to understand. Ideally that website could also produce graphical output
> like pgAdmin does, since that makes it trivially easy to see what the
> 'critical path' is.
I actually started putting something like this together about a year
ago, but the majority of my time was spent reformatting the text rather
than reading the explain.
I've still got a simple perl script that just looks for the most costly
steps in an explain and prints their line-number. Lots of false
positives but it helps to give a starting point for investigations.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Zeugswetter Andreas DCP SD | 2006-04-12 08:57:38 | Re: [PATCHES] schema-qualified SET CONSTRAINTS |
Previous Message | Benny Amorsen | 2006-04-12 07:31:52 | Re: GPUSort project |