From: | markw(at)osdl(dot)org |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org, jenny(at)osdl(dot)org |
Subject: | Re: Proposed Query Planner TODO items |
Date: | 2004-02-09 17:30:04 |
Message-ID: | 200402091730.i19HUHE28069@mail.osdl.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 9 Feb, Tom Lane wrote:
> markw(at)osdl(dot)org writes:
>> http://developer.osdl.org/markw/dbt3-pgsql/
>
>> There's a short summary of the tests I ran over the weekend, with links
>> to detailed retults. Comparing runs 43 (7.4) and 52 (7.5devel), it
>> looks like query #7 had the only significant improvement. Oprofile data
>> should be there too, if that'll help. Let us know if there's anything
>> else we can try for you.
>
> I couldn't figure out anything at all from that, possibly because many
> of the links are dead, eg the "task" descriptions. I don't even see
> where you see the time for query #7.
>
> What would be interesting from my perspective is "explain" results (or
> even better, "explain analyze" results) for the problem queries. Any
> chance of extracting such a thing?
Sorry about the task links, I think I've got that corrected.
I'll see what I can do about the "explain" and "explain analyze"
results. I remember in the past that someone said it would be most
interesting to execute the latter while the test while running, as
opposed to before or after a test. Should I do that here too?
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-02-09 17:33:00 | Re: Proposed Query Planner TODO items |
Previous Message | Tom Lane | 2004-02-09 17:23:22 | Re: Proposed Query Planner TODO items |