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

fix issue #983 #984

Merged
merged 1 commit into from
Dec 27, 2022
Merged

fix issue #983 #984

merged 1 commit into from
Dec 27, 2022

Conversation

eeeebbbbrrrr
Copy link
Contributor

@eeeebbbbrrrr eeeebbbbrrrr commented Dec 27, 2022

A readonly SPI session can now see the database modifications of a previous non-readonly SPI session. This necessitates copying the active snapshot and incrementing its command id when a non-readonly SPI session is done.

Thanks @EdMcBane for finding this and for the unit tests.

A readonly SPI session can now see the database modifications of a previous non-readonly SPI session.  This necessitates copying the active snapshot and incrementing its command id when a non-readonly SPI session is done.
@eeeebbbbrrrr eeeebbbbrrrr merged commit a04559d into develop Dec 27, 2022
@eeeebbbbrrrr eeeebbbbrrrr deleted the issue-983 branch June 20, 2023 17:59
usamoi pushed a commit to tensorchord/pgrx that referenced this pull request Mar 6, 2025
A readonly SPI session can now see the database modifications of a previous non-readonly SPI session.  This necessitates copying the active snapshot and incrementing its command id when a non-readonly SPI session is done.

Thanks @EdMcBane for finding this and for the unit tests.
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

Successfully merging this pull request may close these issues.

1 participant