Re: pg_class.reltuples of brin indexes

Поиск
Список
Период
Сортировка
Искать
От
Masahiko Sawada
Тема
Re: pg_class.reltuples of brin indexes
Дата
Msg-id
CAD21AoAA7+ETUJo=j2L8KAdKF8Q9_5uqwNx6H8rucFm6aRZSBA@mail.gmail.com
Ответ на
Список
Дерево обсуждения
pg_class.reltuples of brin indexes Masahiko Sawada <sawada.mshk@gmail.com>
Re: pg_class.reltuples of brin indexes Tomas Vondra <tomas.vondra@2ndquadrant.com>
Re: pg_class.reltuples of brin indexes Tom Lane <tgl@sss.pgh.pa.us>
Re: pg_class.reltuples of brin indexes Alvaro Herrera <alvherre@alvh.no-ip.org>
Re: pg_class.reltuples of brin indexes Masahiko Sawada <sawada.mshk@gmail.com>
Re: pg_class.reltuples of brin indexes Bruce Momjian <bruce@momjian.us>
Re: pg_class.reltuples of brin indexes Tomas Vondra <tomas.vondra@enterprisedb.com>
Re: pg_class.reltuples of brin indexes Michael Paquier <michael@paquier.xyz>
On Tue, Mar 27, 2018 at 11:28 PM, Alvaro Herrera
 wrote:
> Tom Lane wrote:
>> Tomas Vondra  writes:
>> > I think number of index tuples makes sense, as long as that's what the
>> > costing needs. That is, it's up to the index AM to define it. But it
>> > clearly should not flap like this ...
>>
>> > And it's not just BRIN. This is what I get with a GIN index:
>>
>> Sounds like the same kind of thing we just fixed for SP-GiST :-(
>
> Most likely I modelled the BRIN code after GIN.
>

It's better to create a new index AM that estimates the number of
index tuples, and to update the index stats using that returned value?

Regards,

--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

В списке pgsql-hackers по дате отправления
От: Craig Ringer
Дата:
От: Haribabu Kommi
Дата:
FAQ