-
Notifications
You must be signed in to change notification settings - Fork 19
Copy iterator result in BitmapHeapNext #276
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
Copy iterator result in BitmapHeapNext #276
Conversation
} | ||
else | ||
node->tbmres = tbmres = tbm_shared_iterate(shared_tbmiterator); | ||
tbmres = tbm_shared_iterate(shared_tbmiterator); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we not hold a lock whilst reading from the shared iterator?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, this part of iterator is private to the process - it is not in shared memory.
It allows original code to access this data without any locks
See #275