Prepare 0.9.7 #1182
Merged
Prepare 0.9.7 #1182
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Array iteration was using the wrong tempo for advancing pointers, so arrays with leading nulls sometimes would advance too far.
BradyBonnette
approved these changes
Jun 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is pgrx v0.9.7. It fixes an important bug when working with arrays that have leading NULL elements. Such arrays could lead to spurious Postgres errors or even crashes when iterating.
Please upgrade your pgrx projects as soon as you can, and making sure to update your crate dependencies and to
cargo install cargo-pgrx --locked.What's Changed
PR #1180 - Arrays with leading NULL values are now properly advanced during iteration.
Big thanks to @workingjubilee for some late-night debugging!
Full Changelog: v0.9.6...v0.9.7
NOTE: This cherry-picks the individual commits from PR #1180, updates the version to 0.9.7, and upgrades dependencies. It needs to go straight to
master, after which I'll tag/publish the release and merge back into develop.I'm avoiding releasing all of
developbecause it contains the 16beta1 support and that doesn't need to go out as part of this.