Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id B77B69FA4EE for ; Wed, 18 Oct 2006 17:13:18 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 17035-02 for ; Wed, 18 Oct 2006 17:13:14 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from achille.dalibo.net (achille.dalibo.net [212.85.153.230]) by postgresql.org (Postfix) with ESMTP id B2EF69FA6B2 for ; Wed, 18 Oct 2006 17:13:13 -0300 (ADT) Received: from localhost (localhost.localdomain [127.0.0.1]) by achille.dalibo.net (Postfix) with ESMTP id AC37315F60; Wed, 18 Oct 2006 22:13:11 +0200 (CEST) Received: from achille.dalibo.net ([127.0.0.1]) by localhost (achille [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10286-06; Wed, 18 Oct 2006 22:13:11 +0200 (CEST) Received: from [192.168.2.101] (unknown [84.5.55.48]) by achille.dalibo.net (Postfix) with ESMTP id ADBD415F5E; Wed, 18 Oct 2006 22:13:10 +0200 (CEST) From: Dimitri Fontaine Organization: dalibo To: pgsql-performance@postgresql.org Subject: Re: Postgresql 8.1.4 - performance issues for select on view using max Date: Wed, 18 Oct 2006 22:13:17 +0200 User-Agent: KMail/1.9.5 References: <20061018195134.72985.qmail@web55902.mail.re3.yahoo.com> In-Reply-To: <20061018195134.72985.qmail@web55902.mail.re3.yahoo.com> Cc: Ioana Danes MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1712401.SR6YNxTLng"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200610182213.19037.dim@dalibo.com> X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at dalibo.com X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200610/370 X-Sequence-Number: 21499 --nextPart1712401.SR6YNxTLng Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, Le mercredi 18 octobre 2006 21:51, Ioana Danes a =E9crit=A0: > I am doing a test for a scenario where I have 2 > schemas one (public) for the operational data and > another one (archive) for old, archived data. So > basically I want to split the data from some huge > tables in two. All data before 2006 in archive and all > data after and including 2006 in public. [...] > I got into a scenario where my plan does not work > without doing code change. This sounds a lot as a ddl partitionning, you may want to add some checks t= o=20 your schema and set constraint_exclusion to on in your postgresql.conf. Please read following documentation material : http://www.postgresql.org/docs/8.1/interactive/ddl-partitioning.html Regards, =2D-=20 Dimitri Fontaine http://www.dalibo.com/ --nextPart1712401.SR6YNxTLng Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQBFNorfl4JX7QVNfwQRAi41AJ9lyWwoVtj/9ajzv0FCN/FsSXBQJgCeNbAy EHtdM9UBViPxWcf8LxZFtOk= =Qplu -----END PGP SIGNATURE----- --nextPart1712401.SR6YNxTLng--