X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D1BC356471 for ; Tue, 22 Mar 2005 11:29:26 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 88038-06 for ; Tue, 22 Mar 2005 11:29:24 +0000 (GMT) Received: from fuji.krosing.net (joltid-gw.joltid.org [195.50.194.24]) by svr1.postgresql.org (Postfix) with ESMTP id 4AAC8563E9 for ; Tue, 22 Mar 2005 11:29:22 +0000 (GMT) Received: from fuji.krosing.net (localhost [127.0.0.1]) by fuji.krosing.net (8.13.1/8.13.1) with ESMTP id j2LIW5XN005843; Mon, 21 Mar 2005 20:32:05 +0200 Received: (from hannu@localhost) by fuji.krosing.net (8.13.1/8.13.1/Submit) id j2LIVxLn005842; Mon, 21 Mar 2005 20:31:59 +0200 X-Authentication-Warning: fuji.krosing.net: hannu set sender to hannu@tm.ee using -f Subject: Re: What needs to be done for real Partitioning? From: Hannu Krosing To: Josh Berkus Cc: Stacy White , Tom Lane , Greg Stark , Alvaro Herrera , PFC , pgsql-performance@postgresql.org In-Reply-To: <200503210955.03083.josh@agliodbs.com> References: <200503191202.38089.josh@agliodbs.com> <871xa9fyn4.fsf@stark.xeocode.com> <007401c52dd8$73395450$0200a8c0@grownups> <200503210955.03083.josh@agliodbs.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 21 Mar 2005 20:31:58 +0200 Message-Id: <1111429918.4675.45.camel@fuji.krosing.net> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-1) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200503/433 X-Sequence-Number: 11138 On E, 2005-03-21 at 09:55 -0800, Josh Berkus wrote: > Stacy, > > > Luckily they that had the chance to work with a truly fantastic DBA (the > > author of an Oracle Press performance tuning book even) before they could > > switch back. He convinced them to make some of their indexes global. > > Performance dramatically improved (compared with both the unpartitioned > > schema, and the partitioned-and-locally-indexed schema), and they've since > > stayed with partitioned tables and a mix of local and global indexes. > > Hmmm. Wouldn't Greg's suggestion of a bitmap index which holds information on > what values are found in what partition also solve this? Without 1/2 of > the overhead imposed by global indexes? > > I can actually see such a bitmap as being universally useful to the > partitioning concept ... for one, it would resolve the whole "partition on > {value}" issue. I once (maybe about a year ago) tried to elaborate using bitmap index(es) with page granularity as a tool for simultaneous clustering and lookup for data warehousing using postgres. the main idea was to determine storage location from AND of all "clustered" bitmap indexes and corresponding fast and clustered lookups. This could/should/maybe :) possibly be combined with clustering as well. -- Hannu Krosing