Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id C5D0D1337BFB for ; Thu, 7 Oct 2010 11:29:35 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 19327-03-4 for ; Thu, 7 Oct 2010 14:29:30 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from tamriel.snowman.net (tamriel.snowman.net [72.66.115.51]) by mail.postgresql.org (Postfix) with ESMTP id 7B1BF1337BFC for ; Thu, 7 Oct 2010 11:29:27 -0300 (ADT) Received: by tamriel.snowman.net (Postfix, from userid 1000) id 6BFD622269; Thu, 7 Oct 2010 10:29:27 -0400 (EDT) Date: Thu, 7 Oct 2010 10:29:27 -0400 From: Stephen Frost To: Vincenzo Romano Cc: Robert Haas , Heikki Linnakangas , Simon Riggs , pgsql-hackers@postgresql.org Subject: Re: On Scalability Message-ID: <20101007142927.GT26232@tamriel.snowman.net> References: <1280425184.8613.41.camel@jd-desktop.unknown.charter.com> <1280427410.8613.44.camel@jd-desktop.unknown.charter.com> <4CAD769D.9090301@enterprisedb.com> <1286437290.2304.192.camel@ebony> <4CAD7BED.4050009@enterprisedb.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AtQ9q/eqiCRJOQXg" Content-Disposition: inline In-Reply-To: X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/2.6.26-1-amd64 (x86_64) X-Uptime: 10:28:02 up 406 days, 1:53, 14 users, load average: 0.21, 0.19, 0.09 User-Agent: Mutt/1.5.18 (2008-05-17) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201010/458 X-Sequence-Number: 171498 --AtQ9q/eqiCRJOQXg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline * Vincenzo Romano (vincenzo.romano@notorand.it) wrote: > I see the main problem in the way the planner "understands" which partition > is useful and which one is not. > Having the DDL supporting the feature could just be syntactic sugar > if the underlying mechanism is inadequate. I'm pretty sure the point with the DDL would be to have a way for the user to communicate to the planner more understanding about the partitioning, not just to be syntactic sugar. With that additional information, the planner can make a faster and better decision. Stephen --AtQ9q/eqiCRJOQXg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkyt2UcACgkQrzgMPqB3kiiM1wCfWcfdslE0h3R2BAZhfYB2xlZ5 F+kAnRnAa3XOtDQfGGxZEOccKmhDW0T1 =Uy1Z -----END PGP SIGNATURE----- --AtQ9q/eqiCRJOQXg--