Re: Optimizer improvements: to do or not to do?
От | Peter Eisentraut |
---|---|
Тема | Re: Optimizer improvements: to do or not to do? |
Дата | |
Msg-id | 200609131004.54060.peter_e@gmx.net обсуждение исходный текст |
Ответ на | Re: Optimizer improvements: to do or not to do? ("Say42" <andrews42@yandex.ru>) |
Ответы |
Re: Optimizer improvements: to do or not to do?
|
Список | pgsql-hackers |
Say42 wrote: > Perhaps I am wrong but I assume normalization is a usual case, small > master (parent) tables are not very rare also. > Yes, my example is unusual but it is _real_ and demonstrate PG > optimizer inaccuracy. Why don't we make PG optimizer more close to > reality if we can? Is it so needless and I make a mountain out of a > molehill? All you have shown so far is that one particular query runs faster on your machine when sequential scans are turned off. That is certainly a problem that is worth addressing. But you haven't offered any analysis about the cause of this problem, so any speculation about normalization, usual cases, caching effects and so on are unfounded and premature. -- Peter Eisentraut http://developer.postgresql.org/~petere/
В списке pgsql-hackers по дате отправления: