X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 9A71B9F944D for ; Fri, 12 May 2006 11:05:28 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 71872-06 for ; Fri, 12 May 2006 11:05:19 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id D18C89F9430 for ; Fri, 12 May 2006 11:05:18 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k4CE5GqB023993; Fri, 12 May 2006 10:05:17 -0400 (EDT) To: Antal Attila cc: pgsql-performance@postgresql.org Subject: Re: Wrong plan for subSELECT with GROUP BY In-reply-to: <446482E4.6050906@ritek.hu> References: <446482E4.6050906@ritek.hu> Comments: In-reply-to Antal Attila message dated "Fri, 12 May 2006 14:43:16 +0200" Date: Fri, 12 May 2006 10:05:16 -0400 Message-ID: <23992.1147442716@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/325 X-Sequence-Number: 19112 Antal Attila writes: > If this is a deficiency of the planner, I'd like to suggest this feature > into the planner. This really falls into the category of "you've got to be kidding". There's no way that it'd be reasonable for the planner to expend cycles on every query to look for corner cases like this. Do the hand-optimization instead. regards, tom lane