From: | amihay gonen <agonenil(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org, daphna(dot)litvin(at)gmail(dot)com |
Subject: | Q: How to use indexer api smartly |
Date: | 2014-02-03 14:34:59 |
Message-ID: | CAKb+SBX=YJop9YV+=srLF49zqrZMJZ01U+9jqdr-dnG38vKELA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
My goal is to implement a new index type base on bitmap index algorithm.
I've to main problems :
1. How to get "Target list" - list of columns need to be returned from
query on the index.
I want to implement index only access , today the indexer api get row-id
and then PG retrive the data from the table .
My idea is to return the list of columns directly from the index .
The question is it possible ? how do I know what are the column list
(Assuming the index contain all those columns ).
2. How to implement a query context within the indexer api .
The indexers functions :amcostestimate, ambeginscan and amrescan ) do
not maintain a context.
The idea is the better memory management of index structures ( lock the
memory structure for query life time - until it end)
Thanks ,
Amihay.
From | Date | Subject | |
---|---|---|---|
Next Message | Raphael Bauduin | 2014-02-03 16:10:31 | need of a lateral join with record set returning function? |
Previous Message | Tom Lane | 2014-02-03 14:07:43 | Re: 9.3.2 server creates hundreds of thousands of temporary files |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2014-02-03 14:57:46 | Re: narwhal and PGDLLIMPORT |
Previous Message | Andres Freund | 2014-02-03 14:34:02 | Re: narwhal and PGDLLIMPORT |