Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id AF6B2632B2D for ; Mon, 26 Jul 2010 18:25:43 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 80586-09 for ; Mon, 26 Jul 2010 21:25:35 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from ironport2.lbl.gov (ironport2.lbl.gov [128.3.41.14]) by mail.postgresql.org (Postfix) with ESMTP id 4603C6329E1 for ; Mon, 26 Jul 2010 18:25:36 -0300 (ADT) X-Ironport-SBRS: 4.4 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkkCAI2aTUzRVaA0kGdsb2JhbACDFJAHjEAIFQEBAQEJCQwHEQMfsWaRaYRDcwSECIcj X-IronPort-AV: E=Sophos;i="4.55,263,1278313200"; d="scan'208,217";a="112014281" Received: from mail-pw0-f52.google.com ([209.85.160.52]) by ironport2.lbl.gov with ESMTP; 26 Jul 2010 14:25:30 -0700 Received: by mail-pw0-f52.google.com with SMTP id 7so298280pwi.39 for ; Mon, 26 Jul 2010 14:25:30 -0700 (PDT) Received: by 10.142.127.9 with SMTP id z9mr9549650wfc.125.1280179530322; Mon, 26 Jul 2010 14:25:30 -0700 (PDT) Received: from [128.3.60.152] (cox.lbl.gov [128.3.60.152]) by mx.google.com with ESMTPS id x18sm4660170wfd.20.2010.07.26.14.25.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 26 Jul 2010 14:25:28 -0700 (PDT) Message-ID: <4C4DFD95.4000901@lbl.gov> Date: Mon, 26 Jul 2010 14:26:45 -0700 From: Gerald Fontenay Reply-To: gvfontenay@lbl.gov User-Agent: Thunderbird 1.5.0.5 (X11/20060815) MIME-Version: 1.0 To: pgsql-performance@postgresql.org CC: Gerald Fontenay Subject: Re: Strange explain on partitioned tables References: <4C47F8C8.10005@edd.fr> <4C484874.3060609@2ndquadrant.com> <4C4A11CB.6040800@lbl.gov> <1279923370.9866.37.camel@jd-desktop.unknown.charter.com> In-Reply-To: <1279923370.9866.37.camel@jd-desktop.unknown.charter.com> Content-Type: multipart/alternative; boundary="------------090107000905000703070300" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-4.209 tagged_above=-10 required=5 tests=BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201007/392 X-Sequence-Number: 39781 This is a multi-part message in MIME format. --------------090107000905000703070300 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Joshua D. Drake wrote: > On Fri, 2010-07-23 at 15:03 -0700, Gerald Fontenay wrote: > >>> The PostgreSQL partitioning system is aimed to support perhaps a >>> hundred inherited tables. You can expect to get poor performance on >>> queries if you create 1000 of them. >>> >> Hi, >> >> Why is that you would expect poor performance for say 1000 or more? I >> have a ~1000 inherited tables and I don't see any significant slowdowns. >> I only ever access a single inherited table at a time though in this >> situation. I suppose I am using inheritance only for organization in >> this case... >> > > It is variable based on workload and as I recall has to do with the > planning time. As the number of children increases, so does the planning > time. > > Joshua D. Drake > > > Thank you for your response. So if I query only my target child table, this should be "just like" any other single table wrt planning right? I have thousands of these tables. (I suppose that I'm only using inheritance for the sake of organization in this situation...) Thanks! Gerald --------------090107000905000703070300 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Joshua D. Drake wrote:
On Fri, 2010-07-23 at 15:03 -0700, Gerald Fontenay wrote:
  
The PostgreSQL partitioning system is aimed to support perhaps a 
hundred inherited tables.  You can expect to get poor performance on 
queries if you create 1000 of them. 
      
Hi,

Why is that you would expect poor performance for say 1000 or more? I 
have a ~1000 inherited tables and I don't see any significant slowdowns. 
I only ever access a single inherited table at a time though in this 
situation. I suppose I am using inheritance only for organization in 
this case...
    

It is variable based on workload and as I recall has to do with the
planning time. As the number of children increases, so does the planning
time.

Joshua D. Drake


  
Thank you for your response. So if I query only my target child table, this should be "just like" any other single table wrt planning right? I have thousands of these tables. (I suppose that I'm only using inheritance for the sake of organization in this situation...)

Thanks!
Gerald
--------------090107000905000703070300--