Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id D85169FB5FB for ; Fri, 30 Mar 2007 11:34:21 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 94150-04 for ; Fri, 30 Mar 2007 11:34:07 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from globalrelay.com (mail1.globalrelay.com [204.92.49.200]) by postgresql.org (Postfix) with ESMTP id 851839FB8DB for ; Fri, 30 Mar 2007 11:34:13 -0300 (ADT) X-Virus-Scanned: Scanned by GRC-AntiVirus Gateway X-GR-Acctd: YES X-Real-To: pgsql-performance@postgresql.org, vincenzo.romano@gmail.com Received: from [63.226.156.118] (HELO DaveEMachine) by globalrelay.com (CommuniGate Pro SMTP 4.2.3) with ESMTP id 134264662; Fri, 30 Mar 2007 07:34:11 -0700 From: "Dave Dutcher" To: "'Vincenzo Romano'" , Subject: Re: Weird performance drop Date: Fri, 30 Mar 2007 09:34:10 -0500 Message-ID: <01ea01c772d8$7b87aca0$2e00a8c0@tridecap.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6822 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Thread-Index: AcdylfdqydKDQiXJSWe/qTXphVqvSwAQgetw In-Reply-To: <200703300836.16601.Vincenzo.Romano@gmail.com> Importance: Normal X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/452 X-Sequence-Number: 23857 > From: pgsql-performance-owner@postgresql.org > [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of > Vincenzo Romano > > Is there any "workaround"? > > In my opinion the later the query planner decisions are taken the more > effective they can be. > It could be an option for the function (body) to delay any > query planner > decision. I think a possible workaround is to use a plpgsql function and the execute statement. The docs will have more info. Dave