From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Miroslav Šulc <miroslav(dot)sulc(at)startnet(dot)cz> |
Cc: | pgsql-performance(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PERFORM] How to read query plan |
Date: | 2005-03-14 15:04:25 |
Message-ID: | 13476.1110812665@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
=?windows-1250?Q?Miroslav_=8Aulc?= <miroslav(dot)sulc(at)startnet(dot)cz> writes:
> Tom Lane wrote:
>> Actually, we already had a pending patch (from Atsushi Ogawa) that
>> eliminates that particular O(N^2) behavior in another way. After
>> applying it, I get about a factor-of-4 reduction in the runtime for
>> Miroslav's example.
>>
> Is there a chance we will see this patch in the 8.0.2 release?
No. We are not in the habit of making non-bug-fix changes in stable
branches. Ogawa's patch is in CVS for 8.1.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-03-14 15:09:10 | Re: signed short fd |
Previous Message | Tom Lane | 2005-03-14 15:03:01 | Re: [PERFORM] How to read query plan |
From | Date | Subject | |
---|---|---|---|
Next Message | Miroslav Šulc | 2005-03-14 15:21:37 | Re: [PERFORM] How to read query plan |
Previous Message | Tom Lane | 2005-03-14 15:03:01 | Re: [PERFORM] How to read query plan |