Re: Index-only scans for GIST - Mailing list pgsql-hackers

<div dir="ltr"><br />On Fri, Aug 1, 2014 at 4:58 AM, Anastasia Lubennikova <<a
href="mailto:lubennikovaav@gmail.com">lubennikovaav@gmail.com</a>>wrote:<br />><br />> Hi, hackers!<br />>
Iwork on a GSoC project "Index-only scans for GIST"<br /> > <a
href="https://wiki.postgresql.org/wiki/Support_for_Index-only_scans_for_GIST_GSoC_2014">https://wiki.postgresql.org/wiki/Support_for_Index-only_scans_for_GIST_GSoC_2014</a><br
/>><br/>> Repository is<br />> <a
href="https://github.com/lubennikovaav/postgres/tree/indexonlygist2">https://github.com/lubennikovaav/postgres/tree/indexonlygist2</a><br
/>> Patch is in attachments.<br />><br />> It includes index-only scans for multicolumn GIST and new
regressiontest.<br />> Fetch() method is realized for box and point opclasses. <br />><br />> Documentation is
notupdated yet, but I'm going to do it till the end of GSoC.<br /> ><br />> I've got one question about query
withOR condition. It is the last query in regression test "gist_indexonly". It doesn't fail but it doensn't use
index-onlyscans. Could someone explain to me how it works?<br /> > It seems to depend on build_paths_for_OR
function.But I couldn't understand how.<br />><br /><br />Very nice... please add your patch to the next commit fest
[1].<br/><br />Regards,<br /><br /><br />[1] <a
href="https://commitfest.postgresql.org/action/commitfest_view?id=23">https://commitfest.postgresql.org/action/commitfest_view?id=23</a><br
/><br/>--<br />Fabrízio de Royes Mello<br />Consultoria/Coaching PostgreSQL<br />>> Timbira: <a
href="http://www.timbira.com.br">http://www.timbira.com.br</a><br/>>> Blog sobre TI: <a
href="http://fabriziomello.blogspot.com">http://fabriziomello.blogspot.com</a><br/> >> Perfil Linkedin: <a
href="http://br.linkedin.com/in/fabriziomello">http://br.linkedin.com/in/fabriziomello</a><br/>>> Twitter: <a
href="http://twitter.com/fabriziomello">http://twitter.com/fabriziomello</a></div>