Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skipping evicted tuples in EE PlanNode Executors #157

Open
apavlo opened this issue Jul 9, 2014 · 0 comments
Open

Skipping evicted tuples in EE PlanNode Executors #157

apavlo opened this issue Jul 9, 2014 · 0 comments
Assignees

Comments

@apavlo
Copy link
Owner

apavlo commented Jul 9, 2014

The goal of this task is to allow the EE's runtime engine ignore tuples that are marked as migrated during query execution. This will allow us to delay when we actually remove a tuple from tables and update indexes. This is very similar to how the anti-caching stuff can identify when it's trying to access an evicted tuple and needs to abort the transaction.

There are only four places in the EE that access tuples directly from PersistantTables:

  1. executors/indexscanexecutor
  2. executors/nestloopexecutor
  3. executors/nestloopindexexecutor
  4. executors/seqscanexecutor

If you look at the p_execute() function for each of these classes, you will see a while loop where we iterate over some list of tuples. For IndexScan, you can see where we check TableTuple::isEvicted() for each tuple.

And then this is when I realized that @jdebrabant may not have implemented support for the other parts of the code...

apavlo added a commit that referenced this issue Jul 10, 2014
…d access tracking stuff into the AntiCacheEvictionManager. We now support checking for and updating access tuple accesses in NestLoopIndexScan + SeqScan. Still need to fix NestLoop #157
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants