Bad query optimisation

Поиск
Список
Период
Сортировка
Искать
От
Greg Stark
Тема
Bad query optimisation
Дата
Msg-id
87znrqwu79.fsf@stark.dyndns.tv
Список
Дерево обсуждения
Bad query optimisation Greg Stark <gsstark@mit.edu>

This is weird, it seems like min and max aren't being optimised symmetrically.
It seems like both of these should result in similar plans and run equally
fast. Instead the first is actually really slow and the second is perfectly
quick.



foo=# explain select max(postalcode) from postalcodes where postalcode < 'K0C1N2';

Aggregate  (cost=123.59..123.59 rows=1 width=10) ->  Index Scan using postalcodes_pkey on postalcodes  (cost=0.00..120.50 rows=1234 width=10)


foo=# explain select min(postalcode) from postalcodes where postalcode > 'K0C1N2';

Aggregate  (cost=10373.45..10373.45 rows=1 width=10) ->  Seq Scan on postalcodes  (cost=0.00..9697.11 rows=270535 width=10)

-- 
greg


В списке pgsql-hackers по дате отправления
От: Greg Stark
Дата:
От: Christopher Kings-Lynne
Дата:
Сообщение: Re: Bad query optimisation
FAQ