X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id D19FFD1D07E for ; Wed, 14 Apr 2004 17:12:06 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 86663-05 for ; Wed, 14 Apr 2004 17:12:06 -0300 (ADT) Received: from cmailm3.svr.pol.co.uk (cmailm3.svr.pol.co.uk [195.92.193.19]) by svr1.postgresql.org (Postfix) with ESMTP id 0ECBCD1CCB4 for ; Wed, 14 Apr 2004 17:12:04 -0300 (ADT) Received: from modem-3224.llama.dialup.pol.co.uk ([217.135.188.152] helo=stromboli) by cmailm3.svr.pol.co.uk with esmtp (Exim 4.14) id 1BDqjs-0005CC-Qj; Wed, 14 Apr 2004 21:12:05 +0100 From: "Simon Riggs" To: "Josh Berkus" , Subject: Re: PostgreSQL and Linux 2.6 kernel. Date: Wed, 14 Apr 2004 21:12:18 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-reply-to: <200404050836.52115.josh@agliodbs.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/165 X-Sequence-Number: 6465 > Josh Berkus wrote: > Unfortunately, these days only Tom and Neil seem to be > seriously working on > the query planner (beg pardon in advance if I've missed > someone) so I think > the real answer is that we need another person interested in > this kind of > optimization before it's going to get much better. > Hmmmm. Interesting line of thought. Is the problem "a person interested" or is there another issue there? I was thinking the other day that maybe removing the ability to control join order through explicitly manipulating the FROM clause might actually be counter productive, in terms of longer term improvement of the optimizer. Treating the optimizer as a black box is something I'm very used to from other RDBMS. My question is, how can you explicitly re-write a query now to "improve" it? If there's no way of manipulating queries without actually re-writing the optimizer, we're now in a position where we aren't able to diagnose when the optimizer isn't working effectively. For my mind, all the people on this list are potential "optimizer developers" in the sense that we can all look at queries and see whether there is a problem with particular join plans. Providing good cases of poor optimization is just what's needed to assist those few that do understand the internals to continue improving things. I guess what I'm saying is it's not how many people you've got working on the optimizer, its how many accurate field reports of less-than perfect optimization reach them. In that case, PostgreSQL is likely in a better position than Microsoft, since the accessibility of the pg discussion lists makes such cases much more likely to get aired. Any thoughts? Best Regards, Simon Riggs