Re: Query with large number of joins
От | Marco Di Cesare |
---|---|
Тема | Re: Query with large number of joins |
Дата | |
Msg-id | b0a3ad6dc2194646a776b3a1bcdb3ed3@CO2PR0701MB759.namprd07.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: Query with large number of joins (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: Query with large number of joins
|
Список | pgsql-performance |
On 10/21/2014 12:31 PM, Andrew Dunstan wrote: > Please don't top-post on the PostgreSQL lists. See <http://idallen.com/topposting.html> Oops, sorry. >Have you tried a) either turning off geqo or setting geqo_threshold fairly high b) setting join_collapse_limit fairly high(assuming >all the above join targets are tables and not views, setting it to something like 25 should do the trick. I did try various combinations of these settings but none yielded any significant query run time improvements. > You also haven't told us what settings you have for things like effective_cache_size, which can dramatically affect queryplans. effective_cache_size = 4096MB I tried bumping this up as well but again no significant query run time improvements.
В списке pgsql-performance по дате отправления: