pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hannu Krosing <hannu@tm.ee>
To: Josh Berkus <josh@agliodbs.com>
Cc: Stacy White <harsh@computer.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Greg Stark <gsstark@mit.edu>
Cc: Alvaro Herrera <alvherre@dcc.uchile.cl>
Cc: PFC <lists@boutiquenumerique.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: What needs to be done for real Partitioning?
Date: Mon, 21 Mar 2005 20:31:58 +0200
Message-ID: <1111429918.4675.45.camel@fuji.krosing.net> (raw)
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>

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 <hannu@tm.ee>



view thread (45+ messages)  latest in thread

Message-ID: <1111429918.4675.45.camel@fuji.krosing.net>
Permalink:  ../1111429918.4675.45.camel@fuji.krosing.net/
Also on:    postgresql.org/message-id/1111429918.4675.45.camel@fuji.krosing.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: hannu@tm.ee, josh@agliodbs.com, harsh@computer.org, tgl@sss.pgh.pa.us, gsstark@mit.edu, alvherre@dcc.uchile.cl, lists@boutiquenumerique.com
  Subject: Re: What needs to be done for real Partitioning?
  In-Reply-To: <1111429918.4675.45.camel@fuji.krosing.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox