Re: Improving Inner Join Performance
От | Andy |
---|---|
Тема | Re: Improving Inner Join Performance |
Дата | |
Msg-id | 00b201c612a7$5bca49a0$0b00a8c0@forge обсуждение исходный текст |
Ответ на | Improving Inner Join Performance ("Andy" <frum@ar-sd.net>) |
Список | pgsql-performance |
Sorry, I had to be more specific. VACUUM ANALYZE is performed every hour. Regards, Andy. ----- Original Message ----- From: "Michael Glaesemann" <grzm@myrealbox.com> To: "Andy" <frum@ar-sd.net> Cc: <pgsql-performance@postgresql.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 > >
В списке pgsql-performance по дате отправления: