Changes in amcanreturn() interface to support multicolumn indexes

Поиск
Список
Период
Сортировка
От Anastasia Lubennikova
Тема Changes in amcanreturn() interface to support multicolumn indexes
Дата
Msg-id CAP4vRV7XxvziKV6u7kZt6OoBAmmRX0Pun-h==zDDnzjJ269=yA@mail.gmail.com
обсуждение исходный текст
Ответы Re: Changes in amcanreturn() interface to support multicolumn indexes
Список pgsql-hackers
Changes in amcanreturn() interface to support multicolumn indexes.
Hi, hackers
There is a question of support multicolumn index only scans for GIST.
I need help with this problem.

bool amcanreturn() - function to check whether index supports index-only scans.
Now it's defined for 
- B-tree. It always returns true, so there's no questions.
- SP-GIST. It doesn't support multicolumn indexes, so there's no problems in spgcanreturn too.

- GIST. In first version it works only for onecolumn indexes. gistcanreturn() checks whether fetch() method is defined for column's data type.

There is a question of support multicolumn index only scans for GIST.
gistcanreturn() can return true if fetch is implemented for all indexed columns and false otherwise.
But that's not very good case for multicolumn indexes.

I think, it requires extend the interface to add separate columns checking.
But I can't understand what kind of changes is required 
and how would it affect on previous amcanreturn interface.


--
Regards,
Lubennikova Anastasia

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

Предыдущее
От: Christoph Berg
Дата:
Сообщение: Re: postgresql.auto.conf and reload
Следующее
От: David Rowley
Дата:
Сообщение: Re: Allowing join removals for more join types