Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id 5874C1337BB9
	for <pgsql-hackers-postgresql.org@mail.postgresql.org>;
	Thu,  7 Oct 2010 12:12:55 -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 19503-02
	for <pgsql-hackers-postgresql.org@mail.postgresql.org>;
	Thu,  7 Oct 2010 15:12:47 +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 E791C1337B50
	for <pgsql-hackers@postgresql.org>;
	Thu,  7 Oct 2010 12:12:45 -0300 (ADT)
Received: by tamriel.snowman.net (Postfix, from userid 1000)
	id CDD3C22294; Thu,  7 Oct 2010 11:12:44 -0400 (EDT)
Date: Thu, 7 Oct 2010 11:12:44 -0400
From: Stephen Frost <sfrost@snowman.net>
To: Vincenzo Romano <vincenzo.romano@notorand.it>
Cc: Greg Smith <greg@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>,
	Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>,
	Simon Riggs <simon@2ndquadrant.com>, pgsql-hackers@postgresql.org
Subject: Re: On Scalability
Message-ID: <20101007151244.GV26232@tamriel.snowman.net>
References: <1280427410.8613.44.camel@jd-desktop.unknown.charter.com>
	<AANLkTimSGghp4TseAV-zgNYakkyH3J_jW2k8peL7EOTv@mail.gmail.com>
	<4CAD769D.9090301@enterprisedb.com>
	<1286437290.2304.192.camel@ebony>
	<4CAD7BED.4050009@enterprisedb.com>
	<AANLkTi==OD9afGEDOm7OY3KYydLXcMj=kO7M5+QFbaM0@mail.gmail.com>
	<AANLkTiktPBVfa950ntGVDroY8ZNR1npQaA-oPnAJSn7n@mail.gmail.com>
	<AANLkTi=ZH-bBoXhsMf0Nj9xxmjoTCTj5Sjgk1cR1h-SH@mail.gmail.com>
	<4CADDA06.5070002@2ndquadrant.com>
	<AANLkTi=ZorrHqQeeYT1kRUiTFNKdpHqg4StBwLLWG6OT@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="iRQTiiVA1juStYAd"
Content-Disposition: inline
In-Reply-To: <AANLkTi=ZorrHqQeeYT1kRUiTFNKdpHqg4StBwLLWG6OT@mail.gmail.com>
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: 11:06:50 up 406 days,  2:31, 14 users,  load average: 0.00, 0.09,
	0.12
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/468
X-Sequence-Number: 171508


--iRQTiiVA1juStYAd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

* Vincenzo Romano (vincenzo.romano@notorand.it) wrote:
> I would expect a parser to ... ehm ... parse the CHECK constraint
> expression at "CREATE TABLE " time and
> extract all the needed "high quality metadata", like the list of
> columns involved and the type of
> checks (range, value list, etc.).

Check constraints can be added after the table is created.  Inheiritance
can be added/changed independently of check constraints.  Hacking all of
the inheiritance, check constraint creation, and any other possibly
involved code paths to try to figure out if this particular table, check
constraint, inheiritance relationship, etc, is part of a partitioning
setup isn't exactly trivial, or the right approach.

	Thanks,

		Stephen

--iRQTiiVA1juStYAd
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)

iEYEARECAAYFAkyt42wACgkQrzgMPqB3kijMcwCfQdHLNyi0vgDnX4Drh5Ni+k0s
c8gAn3vO207d2DZJPo60GvWf+AUyOHxK
=rfe5
-----END PGP SIGNATURE-----

--iRQTiiVA1juStYAd--