X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id A8AA211F6648 for ; Wed, 26 Apr 2006 19:51:26 -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 41540-07-2 for ; Wed, 26 Apr 2006 19:50:43 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 0D2AD11F674B for ; Wed, 26 Apr 2006 19:50:42 -0300 (ADT) Received: by noel.decibel.org (Postfix, from userid 1001) id 16D7A56431; Wed, 26 Apr 2006 17:50:37 -0500 (CDT) Received: (hashcash-sendmail, from uid 1001); Wed, 26 Apr 2006 17:50:36 -0500 Date: Wed, 26 Apr 2006 17:50:36 -0500 From: "Jim C. Nasby" To: Chris Hoover Cc: Benjamin Krajmalnik , pgsql-admin@postgresql.org Subject: Re: Tale partitioning Message-ID: <20060426225036.GG97354@pervasive.com> References: <8511B4970E0D124898E973DF496F9B432515C3@stash.stackdump.local> <1d219a6f0604261333u1e0a2c0btb7786f3c32360f27@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1d219a6f0604261333u1e0a2c0btb7786f3c32360f27@mail.gmail.com> X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060426:revoohc@gmail.com::1MBAoRc+63PfGLMX:00000000000000000000 0000000000000000000000002o0Z X-Hashcash: 1:20:060426:kraj@illumen.com::w2TQpDFXNwrQitO2:02Vsv X-Hashcash: 1:20:060426:pgsql-admin@postgresql.org::eVIfU6oV7SGn6MaX:00000000000 0000000000000000000000001Ydc X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/290 X-Sequence-Number: 21459 On Wed, Apr 26, 2006 at 04:33:04PM -0400, Chris Hoover wrote: > Each of the partition tables needs it's own set of indexes. Build them, and > see if the does not fix your performance issues. Also, be sure you turned > on the constraint_exclusion parameter, and each table (other than the > "master") has an constraint on it that is unique. I don't believe constraint_exclusion is smart enough to deal with ORDER BY / LIMIT yet... :/ -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461