Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id C0D7463263A for ; Mon, 8 Mar 2010 17:56:15 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 14877-03 for ; Mon, 8 Mar 2010 21:56:05 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mail.postgresql.org (Postfix) with ESMTP id 1709F63219C for ; Mon, 8 Mar 2010 17:56:04 -0400 (AST) Received: by fg-out-1718.google.com with SMTP id l26so1382676fgb.1 for ; Mon, 08 Mar 2010 13:56:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=kfKdojPdCGcL+EClin+XESilQ3HOuogH5DM9jpYeikg=; b=xUvna9RqLDnNdXLQLr4n10jT80Qeo5LOek7RTgbmhzwZgfkdeXooweQdiIwNkWlOo2 ccZ7Si/BU3ojwIufoqmm9UOKp9PH1At5T6WI+7k6aWlMG1VSp3ier6aAVwziTWxip7p8 34NXQVC2OJJ/foehhN/sPPl8UlD+BKHdVl6Pc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=xJb9aNn+8vhfwzftXnie+ytt7ed8DndBq8Sou0FUaImmC9HoAy2NDzQWNI4mKfoK8Z A6ZG4MaNzuCtXa92+viMOv8esxNnLaJ0/I8QKlPCUzlg0y/DnOufA4eEjVGUalfAegqL UOe1I8Yc6umBL09DkV9QR0YEvQO4y1g/h8STA= MIME-Version: 1.0 Received: by 10.239.185.19 with SMTP id a19mr440961hbh.159.1268085363329; Mon, 08 Mar 2010 13:56:03 -0800 (PST) In-Reply-To: <4B93E906.5030804@agliodbs.com> References: <4B8ACFE7.6040207@agliodbs.com> <603c8f071003030912k5750abadif64cb36d67ab99ae@mail.gmail.com> <4B8ED891.7060405@agliodbs.com> <603c8f071003031807p52f136edh683d19a1d5b46660@mail.gmail.com> <4B93E906.5030804@agliodbs.com> Date: Mon, 8 Mar 2010 16:56:03 -0500 Message-ID: <603c8f071003081356p123274cep45ae89f4509e56d4@mail.gmail.com> Subject: Re: Estimation issue with partitioned tables From: Robert Haas To: Josh Berkus Cc: pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.443 tagged_above=-10 required=5 tests=BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156 X-Spam-Level: X-Archive-Number: 201003/80 X-Sequence-Number: 37905 On Sun, Mar 7, 2010 at 12:57 PM, Josh Berkus wrote: >>> Yeah, I can generate one pretty easily; the behavior is readily >>> observable and repeatable. =A0Will get on it RSN, but at you said, we'r= e >>> not doing anything about it for 9.0. > > Well, I can generate a test case, but on examination it turns out to be > nothing to do with partitioning; it's just good old "n-distinct > underestimation", and not really related to partitioning or joins. Ah. Well in 9.0 there will be a work around, by me as it happens. :-) ...Robert