From: | Anastasia Lubennikova <lubennikovaav(at)gmail(dot)com> |
---|---|
To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Index-only scans for GIST |
Date: | 2014-08-01 07:58:38 |
Message-ID: | CAP4vRV4xiK7v4XQgdmtOco9WB2mYeTEgbncF-DrMRYGvDk8V3w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi, hackers!
I work on a GSoC project "Index-only scans for GIST"
https://wiki.postgresql.org/wiki/Support_for_Index-only_scans_for_GIST_GSoC_2014
Repository is
https://github.com/lubennikovaav/postgres/tree/indexonlygist2
Patch is in attachments.
It includes index-only scans for multicolumn GIST and new regression test.
Fetch() method is realized for box and point opclasses.
Documentation is not updated yet, but I'm going to do it till the end of
GSoC.
I've got one question about query with OR condition. It is the last query
in regression test "gist_indexonly". It doesn't fail but it doensn't use
index-only scans. Could someone explain to me how it works?
It seems to depend on build_paths_for_OR
<http://doxygen.postgresql.org/indxpath_8c.html#ae660d2e886355e53ed3b9ec693e4afd2>
function.
But I couldn't understand how.
--
Best regards,
Lubennikova Anastasia
Attachment | Content-Type | Size |
---|---|---|
indexonlyscan_gist.patch | application/octet-stream | 49.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro HORIGUCHI | 2014-08-01 09:10:55 | Re: Introducing coarse grain parallelism by postgres_fdw. |
Previous Message | Mitsumasa KONDO | 2014-08-01 07:58:01 | Re: gaussian distribution pgbench -- splits v4 |