Re: Improving Inner Join Performance

From: Andy
Subject: Re: Improving Inner Join Performance
Date: ,
Msg-id: 00b201c612a7$5bca49a0$0b00a8c0@forge
(view: Whole thread, Raw)
In response to: Improving Inner Join Performance  ("Andy")
List: pgsql-performance

Tree view

Improving Inner Join Performance  ("Andy", )
 Re: Improving Inner Join Performance  (Frank Wiles, )
 Re: Improving Inner Join Performance  ("Andy", )
  Re: Improving Inner Join Performance  (Michael Glaesemann, )
 Re: Improving Inner Join Performance  ("Andy", )
 Re: Improving Inner Join Performance  (Pandurangan R S, )
 Re: Improving Inner Join Performance  ("Andy", )
  Re: Improving Inner Join Performance  (Jaime Casanova, )
 Re: Improving Inner Join Performance  ("Andy", )
  Re: Improving Inner Join Performance  ("Jim C. Nasby", )

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

Regards,
Andy.

----- Original Message -----
From: "Michael Glaesemann" <>
To: "Andy" <>
Cc: <>
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
>
>


pgsql-performance by date:

From: "Andy"
Date:
Subject: Re: Improving Inner Join Performance
From: Ian Westmacott
Date:
Subject: Re: improving write performance for logging