Re: Improving Inner Join Performance

From: "Andy" <frum(at)ar-sd(dot)net>
To: "Michael Glaesemann" <grzm(at)myrealbox(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Improving Inner Join Performance
Date: 2006-01-06 09:54:46
Message-ID: 00b201c612a7$5bca49a0$0b00a8c0@forge
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Sorry, I had to be more specific.
VACUUM ANALYZE is performed every hour.

Regards,
Andy.

----- Original Message -----
From: "Michael Glaesemann" <grzm(at)myrealbox(dot)com>
To: "Andy" <frum(at)ar-sd(dot)net>
Cc: <pgsql-performance(at)postgresql(dot)org>
Sent: Friday, January 06, 2006 11:45 AM
Subject: Re: [PERFORM] Improving Inner Join 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
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
>

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Pandurangan R S 2006-01-06 09:56:31 Re: Improving Inner Join Performance
Previous Message Michael Glaesemann 2006-01-06 09:45:06 Re: Improving Inner Join Performance