Re: Improving Inner Join Performance

From: Michael Glaesemann <grzm(at)myrealbox(dot)com>
To: "Andy" <frum(at)ar-sd(dot)net>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Improving Inner Join Performance
Date: 2006-01-06 09:45:06
Message-ID: 10D92D77-0DC5-4772-98CD-A6799E3A39C8@myrealbox.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


On Jan 6, 2006, at 18:21 , Andy wrote:

> Yes I have indexes an all join fields. The tables have around 30
> columns each and around 100k rows. The database is vacuumed every
> hour.

Just to chime in, VACUUM != VACUUM ANALYZE. ANALYZE is what updates
database statistics and affects query planning. VACUUM alone does not
do this.

>> Do you have an index on report.id_order ? Try creating an index for
>> it if not and run a vacuum analyze on the table to see if it gets
>> rid of the sequence scan in the plan.

Michael Glaesemann
grzm myrealbox com

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Andy 2006-01-06 09:54:46 Re: Improving Inner Join Performance
Previous Message Andy 2006-01-06 09:21:31 Re: Improving Inner Join Performance