Re: RT3.4 query needed a lot more tuning with 9.2 than it did with 8.1

Поиск
Список
Период
Сортировка
От Christoph Berg
Тема Re: RT3.4 query needed a lot more tuning with 9.2 than it did with 8.1
Дата
Msg-id 20130515064819.GD704@msgid.df7cb.de
обсуждение исходный текст
Ответ на Re: RT3.4 query needed a lot more tuning with 9.2 than it did with 8.1  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-performance
Re: Tom Lane 2013-05-06 <1583.1367858328@sss.pgh.pa.us>
> The newer rowcount estimates are much further away from reality:
>
> >  Unique  (cost=1117.67..1118.46 rows=9 width=1115) (actual time=82.646..85.695 rows=439 loops=1)
>
> >  Unique  (cost=784205.94..796940.08 rows=145533 width=1061) (actual time=9710.683..9713.175 rows=439 loops=1)
>
> Has the new DB been analyzed?  Maybe you had custom stats targets in
> the old DB that didn't get copied to the new one?

The new DB was analyzed with various stats targets, including values
that were higher that anything we would have used in 8.1. I don't
think we had per-table settings in there (the actual DB is now gone
for good).

Christoph
--
cb@df7cb.de | http://www.df7cb.de/


В списке pgsql-performance по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Lock and pg_stat
Следующее
От: Christoph Berg
Дата:
Сообщение: Re: RT3.4 query needed a lot more tuning with 9.2 than it did with 8.1