fix: upgrade pg_textsearch to include ResourceOwnerEnlarge crash fix#3
Merged
pyramation merged 1 commit intomainfrom Mar 4, 2026
Merged
Conversation
Upgrades pg_textsearch to include the ResourceOwnerEnlarge crash fix from PR #248 (issue #247). The crash occurs when a BM25 index scan runs inside a transaction that is rolled back. Changes: - Pin pg_textsearch to commit ae1c221 on main (no tagged release includes the fix yet; latest release is v0.5.1) - Remove the math.h sed workaround (fixed upstream in v0.3.0) - Clone full repo instead of shallow tag clone (needed for commit checkout)
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
This file contains hidden or 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
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.
Summary
Upgrades pg_textsearch from v0.2.0 to main@ae1c221 to include the fix for issue #247 / PR #248 — a crash where BM25 index scans inside rolled-back transactions trigger
ResourceOwnerEnlarge called after release started, killing the PostgreSQL server.The fix is not included in any tagged release yet (latest is v0.5.1), so we pin to the specific merge commit on
main. The oldmath.hsed workaround is removed (fixed upstream since v0.3.0).Review & Testing Checklist for Human
make test). This has not been tested — we're jumping from v0.2.0 to post-v0.5.1, which is a major version leap.REINDEXor drop/recreate all BM25 indexes in any running environments.ae1c221resolves correctly. Consider pinning to the full 40-character SHA for safety against future collisions.--depth 1(shallow, fast) to a full clone (entire repo history). Consider adding--depth Nor--single-branchto keep build times reasonable.Notes