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=rmyRqqKHWiLNuXm/KUfxEk1+Kdttsw0QBBhAFSZSSFi3sjNjXLw9L287B2i7AaD8k6
	QJGbSXtmjFQcPKGdsGjwzDOSZ/0N1jAOonS0Ye6vPMIweyoeoU//SqtwqhOFNXDlwbTH
	kBI9rmmWdINamwoob9OzSzY44rhfx13RcVSyA=
MIME-Version: 1.0
In-Reply-To: <4B8ED891.7060405@agliodbs.com>
References: <4B8ACFE7.6040207@agliodbs.com>
	<603c8f071003030912k5750abadif64cb36d67ab99ae@mail.gmail.com>
	<4B8ED891.7060405@agliodbs.com>
Date: Wed, 3 Mar 2010 21:07:11 -0500
Message-ID: <603c8f071003031807p52f136edh683d19a1d5b46660@mail.gmail.com>
Subject: Re: Estimation issue with partitioned tables
From: Robert Haas <robertmhaas@gmail.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 3, 2010 at 4:45 PM, Josh Berkus <josh@agliodbs.com> wrote:
>> I feel like I've seen these way-too-high row estimates in some other
>> postings to -performance, but I'm not sure if it was the same issue.
>> You don't by chance have a RTC? I don't think it's likely fixed in 9.0
>> but it would be interesting to investigate.
>
> Yeah, I can generate one pretty easily; the behavior is readily
> observable and repeatable. =A0Will get on it RSN, but at you said, we're
> not doing anything about it for 9.0.
>
> I've a feeling that this will become one of the list of issues to be
> fixed with 'real partitioning'.

I can believe it.  I can't promise anything, but like I say I'm
willing to take a poke at it if you can provide me a test case.

...Robert