X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id BA48B9DCDB8 for ; Fri, 10 Feb 2006 21:47:35 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 59877-03-4 for ; Fri, 10 Feb 2006 21:47:38 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.197]) by postgresql.org (Postfix) with ESMTP id 45FB79DCDE7 for ; Fri, 10 Feb 2006 21:47:30 -0400 (AST) Received: by uproxy.gmail.com with SMTP id s2so195762uge for ; Fri, 10 Feb 2006 17:47:35 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=MGwkkamFzobH/TNBCj6G1DXS1dQsQ9c5CbSMKEPxuNyRT9CxM2z7WKpMgFdHUG0hkweZoW76pLWdgx7VWZgtHmJRtU4VuJAlhD3OwRzyP2QaI7GYsaESc490fFkeVqNPJgPn58l46YVOpM6/mvlZHyQ7wZJAseda9N7mTL25VJM= Received: by 10.66.243.20 with SMTP id q20mr19760ugh; Fri, 10 Feb 2006 17:47:34 -0800 (PST) Received: by 10.66.244.2 with HTTP; Fri, 10 Feb 2006 17:47:34 -0800 (PST) Message-ID: Date: Fri, 10 Feb 2006 20:47:34 -0500 From: uwcssa To: pgsql-admin@postgresql.org Subject: gepo optimizer question MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4356_3845887.1139622454760" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=1.669 required=5 tests=[AWL=-0.609, HTML_10_20=0.945, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.332] X-Spam-Score: 1.669 X-Spam-Level: * X-Archive-Number: 200602/119 X-Sequence-Number: 20540 ------=_Part_4356_3845887.1139622454760 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I have a question with regard to GEQO optimizer of Postgresql. For complex queries with over 12 tables in a join, (12 is the default value), the Postgresql optimizer will not use the dynamic programming style optimizer. Instead, it uses genetic algorithm to compute a sub-optimal quer= y plan. The reason is that GEQO takes sub-seconds to find a query plan while the DP style optimizer will take minutes or even hours to optimize a comple= x query with large join degree. I am wondering if anyone here ever had complex queries that the GEQO fails to work properly, i.e., finds a terrible query plan as compared to one found by DP optimizer (by forcing Postgresql always uses DP). This is important to me since I am trying to see what type of queries will be worth spending a lot of time doing a thorough DP optimization (if it is going to be executed again and again). thanks a lot! ------=_Part_4356_3845887.1139622454760 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
I have a question with regard to GEQO optimizer of Postgresql.
 
For complex queries with over 12 tables in a join, (12 is the default = value), the Postgresql optimizer will not use the dynamic programming = style optimizer. Instead, it uses genetic algorithm to compute a sub-optima= l query plan.  The reason is that GEQO takes sub-seconds to find a que= ry plan while the DP style optimizer will take minutes or even hours to opt= imize a complex query with large join degree.
 
I am wondering if anyone here ever had complex queries that the GEQO f= ails to work properly, i.e.,  finds a terrible query plan as compared = to one found by DP optimizer (by forcing Postgresql always uses DP). &= nbsp;  This is important to me since I am trying to see what type of q= ueries will be worth spending a lot of time doing a thorough DP optimizatio= n (if it is going to be executed again and again).
 
thanks a lot!
------=_Part_4356_3845887.1139622454760--