X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id EC90D5665F; Mon, 14 Mar 2005 15:04:21 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 47222-07; Mon, 14 Mar 2005 15:04:21 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id AAB235668A; Mon, 14 Mar 2005 15:04:20 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j2EF4PIP013477; Mon, 14 Mar 2005 10:04:25 -0500 (EST) To: =?windows-1250?Q?Miroslav_=8Aulc?= Cc: pgsql-performance@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: [PERFORM] How to read query plan In-reply-to: <42354F00.5060904@startnet.cz> References: <42345D24.8070104@startnet.cz> <4234692E.3050802@arbash-meinel.com> <42347407.2000202@startnet.cz> <423478B1.7080106@arbash-meinel.com> <18381.1110741354@sss.pgh.pa.us> <423497FE.6040908@startnet.cz> <19293.1110743673@sss.pgh.pa.us> <42349C96.60401@startnet.cz> <3174.1110745587@sss.pgh.pa.us> <4234AF56.1040509@startnet.cz> <6715.1110758921@sss.pgh.pa.us> <4850.1110776411@sss.pgh.pa.us> <42354F00.5060904@startnet.cz> Comments: In-reply-to =?windows-1250?Q?Miroslav_=8Aulc?= message dated "Mon, 14 Mar 2005 09:44:48 +0100" Date: Mon, 14 Mar 2005 10:04:25 -0500 Message-ID: <13476.1110812665@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/445 X-Sequence-Number: 65247 =?windows-1250?Q?Miroslav_=8Aulc?= 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