Postgres Pro
Downloads
Home   >   mailing lists

Re: Proposal: scan key push down to heap [WIP] - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: Proposal: scan key push down to heap [WIP]
Date
Msg-id CAFiTN-tJ8fQwOe+EzBpcG0Joxtuj9vMGKNu5_e6iCP8_0wzeDg@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: scan key push down to heap [WIP]  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Proposal: scan key push down to heap [WIP]  (Dilip Kumar <dilipbalaut@gmail.com>)
List pgsql-hackers
Tree view 
On Mon, Nov 14, 2016 at 9:30 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> Couldn't we just change the current memory context before calling
> heap_getnext()?  And then change back?

Right, seems like it will not have any problem..
>
> Also, what if we abandoned the idea of pushing qual evaluation all the
> way down into the heap and just tried to do HeapKeyTest in SeqNext
> itself?  Would that be almost as fast, or would it give up most of the
> benefits?
This we can definitely test. I will test and post the data.

Thanks for the suggestion.

-- 
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Proposal: scan key push down to heap [WIP]
Next
From: Tom Lane
Date:
Subject: Re: Pinning a buffer in TupleTableSlot is unnecessary