Re: WIP: BRIN multi-range indexes
От | Alexander Korotkov |
---|---|
Тема | Re: WIP: BRIN multi-range indexes |
Дата | |
Msg-id | CAPpHfdsUSu+tEo6Kaj_iXvrhzhGOZ2pkYEn_aWj9b4M2vHGEhg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: WIP: BRIN multi-range indexes (Tomas Vondra <tomas.vondra@2ndquadrant.com>) |
Ответы |
Re: WIP: BRIN multi-range indexes
|
Список | pgsql-hackers |
On Sun, Mar 4, 2018 at 3:15 AM Tomas Vondra <tomas.vondra@2ndquadrant.com> wrote: > I've been thinking about this after looking at 0a459cec96, and I don't > think this patch has the same issues. One reason is that just like the > original minmax opclass, it does not really mess with the data it > stores. It only does min/max on the values, and stores that, so if there > was NaN or Infinity, it will index NaN or Infinity. FWIW, I think the closest similar functionality is subtype_diff function of range type. But I don't think we should require range type here just in order to fetch subtype_diff function out of it. So, opclass distance function looks OK for me, assuming it's not AM-defined function, but function used for inter-opclass compatibility. ------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
В списке pgsql-hackers по дате отправления: