Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 374549FB2C4 for ; Mon, 30 Oct 2006 18:47:14 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 08953-08 for ; Mon, 30 Oct 2006 18:47:09 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail01.enterprisedb.com (mail01.enterprisedb.com [63.246.7.168]) by postgresql.org (Postfix) with ESMTP id 185589FA48B for ; Mon, 30 Oct 2006 18:47:08 -0400 (AST) thread-index: Acb8dVTLoAG+3GwkSr+V2BWiYHmJBw== Received: from [192.168.0.20] ([62.232.55.118]) by mail01.enterprisedb.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 30 Oct 2006 17:47:06 -0500 Subject: Re: partitioned table performance Content-Class: urn:content-classes:message Importance: normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757 From: "Simon Riggs" To: "Andreas Kostyrka" Cc: In-Reply-To: <1162245495.8515.7.camel@andi-lap> References: <1162074485.16385.93.camel@andi-lap> <1162196302.11568.221.camel@silverbirch.site> <1162245495.8515.7.camel@andi-lap> Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 30 Oct 2006 22:46:43 +0000 Message-ID: <1162248403.11568.370.camel@silverbirch.site> MIME-Version: 1.0 X-Mailer: Evolution 2.6.0 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 30 Oct 2006 22:47:07.0328 (UTC) FILETIME=[53C2B400:01C6FC75] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200610/620 X-Sequence-Number: 21749 On Mon, 2006-10-30 at 22:58 +0100, Andreas Kostyrka wrote: > Am Montag, den 30.10.2006, 08:18 +0000 schrieb Simon Riggs: > > On Sun, 2006-10-29 at 00:28 +0200, Andreas Kostyrka wrote: > > > > > Any ideas how to make the optimizer handle partitioned tables more > > > sensible? > > > > Yes, those are known inefficiencies in the current implementation which > > we expect to address for 8.3. > > Any ideas to force the current optimizer to do something sensible? Brute force & ignorance: PL/pgSQL Perhaps some other domain knowledge might help you shorten the search? Thats all for now. It's not a minor fixup and nobody had time to fix that for 8.2 since other fish were bigger. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com