From: | <alvis(at)piladzi-2(dot)biz> |
---|---|
To: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | When NOT to index small tables? |
Date: | 2003-08-20 10:01:16 |
Message-ID: | 004201c36701$fffee930$1401010a@Xeon |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
I have found many reasons not to index small tables (see .
But I still have questions.
1. How small is small enough?
2. am I supposed to drop primary key index on so called 'label tables'
knowing I am using this pk in join clause?
3. Is it good to drop index on small table If I know I have created VIEW and
joined large table and the small one
and I have where condition on that particular colum?
Ilustrative example:
table small
{
id -- primary key
colum_for_where_condition -- index or not to index?
}
table large
{
...
fk_for_small_table -- indexed
...
}
create view as select .....
inner join on common_column ..
I have migrated from mysql .
I have found that complex view expression takes about 10 sec using ordinary
planner,
but genetic alg takes about 5 sec. Strange?
I can give details if someone is interested.
Regards,
Alvis
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2003-08-20 13:36:24 | Re: When NOT to index small tables? |
Previous Message | Shridhar Daithankar | 2003-08-19 06:33:26 | Re: Insert performance |