Re: Index-only-scans, indexam API changes
От
Heikki Linnakangas
Тема
Re: Index-only-scans, indexam API changes
Дата
Msg-id
4A5B4CC6.9020702@enterprisedb.com
Ответ на
Re: Index-only-scans, indexam API changes (Tom Lane)
Список
Дерево обсуждения
Index-only-scans, indexam API changes Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: Index-only-scans, indexam API changes Tom Lane <tgl@sss.pgh.pa.us>
Re: Index-only-scans, indexam API changes Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: Index-only-scans, indexam API changes Tom Lane <tgl@sss.pgh.pa.us>
Re: Index-only-scans, indexam API changes Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Re: Index-only-scans, indexam API changes Robert Haas <robertmhaas@gmail.com>
Re: Index-only-scans, indexam API changes Teodor Sigaev <teodor@sigaev.ru>
Re: Index-only-scans, indexam API changes Greg Stark <gsstark@mit.edu>
Tom Lane wrote: > Heikki Linnakangas writes: >> At the moment, amgettuple only returns pointers to heap tuples. There is >> no way to return data from the index tuples. That needs to be changed to >> support index-only scans. > > What are you going to do for index types that don't store the original > data (e.g. hash)? They will obviously not be able to regurgitate index tuples. I have not yet decided how that's going to be signaled. In the prototype patch I have, I have hard-coded that only b-trees can do that. A new column "amcanreturntuples" column in pg_am seems like the most straightforward way. (This indexam API patch isn't bothered with that yet. It just splits index_gettuple() into two) -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления