Index occupancy

From: "tschak" <jochen(dot)schlosser(at)gmail(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Index occupancy
Date: 2006-02-02 14:03:01
Message-ID: 1138888981.186497.321210@z14g2000cwz.googlegroups.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Hi everyone,

I have a question concerning the size of an index...
What I acually did was bulid a btree index on an smallint attribute
within a table with 10^8 rows. The table itself is app. 10GB large and
what I would like to have the smallest possible indeces. Unfortunately
the current size is about 2GB per indexed column (8 columns are indexed
in total) which is too large if the planner is supposed to choose a
bitmap scan between all of the indices.

So what I would like to know is the following:
Is there an easy way to tell postgres to occupy the index pages up to
100 %?
I am working in a decision support system so inserts/deletes etc. do
normally not happen at all?

Thanks,

Tschak

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Marc Morin 2006-02-02 16:27:38 Re: partitioning and locking problems
Previous Message Markus Schaber 2006-02-02 12:44:23 Re: partitioning and locking problems