Re: Optimizer misses big in 10.4 with BRIN index

Поиск
Список
Период
Сортировка
От Emre Hasegeli
Тема Re: Optimizer misses big in 10.4 with BRIN index
Дата
Msg-id CAE2gYzzgQP3tMMPaR-xPCrTpC8_afGnBOO3EaD6bDEQBn3UNQA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Optimizer misses big in 10.4 with BRIN index  (David Rowley <david.rowley@2ndquadrant.com>)
Ответы Re: Optimizer misses big in 10.4 with BRIN index  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Список pgsql-hackers
> Isn't the 23040 just the totalpages * 10 per `return totalpages * 10;`
> in bringetbitmap()?

Yes, it is just confusing.  The correct value is on one level up of
the tree.  It is 204 + 4404 rows removed by index recheck = 4608, so
the estimate is not only 150x but 733x off :(.

The sequential scan plan shows 204 + 1125498 rows removed by filter =
1125702 as the actual table size.  However the former plan estimates
to get 3377106 rows from the index.  That is 3x of the table size.
The selectivity estimation cannot be greater than 1.  If I am not
missing anything, the general statistics of this table should be
seriously outdated.


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

Предыдущее
От: Oleksandr Shulgin
Дата:
Сообщение: Re: How can we submit code patches that implement our (pending) patents?
Следующее
От: Ibrar Ahmed
Дата:
Сообщение: Re: Log query parameters for terminated execute