Re: Join Query Perfomance Issue
| От | Scott Marlowe |
|---|---|
| Тема | Re: Join Query Perfomance Issue |
| Дата | |
| Msg-id | dcc563d10802131336s366d66c6kcb9f1fd23818552b@mail.gmail.com обсуждение |
| Ответ на | Re: Join Query Perfomance Issue (Thomas Zaksek <zaksek@ptt.uni-due.de>) |
| Ответы |
Re: Join Query Perfomance Issue
|
| Список | pgsql-performance |
On Feb 12, 2008 4:11 AM, Thomas Zaksek <zaksek@ptt.uni-due.de> wrote: > I tried turning off nestloop, but with terrible results: Yeah, it didn't help. I was expecting the query planner to switch to a more efficient join plan. > I also tried to increase work_men, now the config is > work_mem = 4MB Try setting it higher for JUST THIS query. i.e. set work_mem=128M; explain analyze select .... and see how that runs. Then play with it til you've got it down to what helps. Note that work_mem in postgresql.conf being too large can be dangerous, so it might be something you set for just this query for safety reasons.
В списке pgsql-performance по дате отправления: