Merged
Conversation
- Update version from 1.0.0-dev to 0.6.0 across all files - Rename SQL files and banner image for release - Add 0.5.1→0.6.0 upgrade path - Replace prerelease WARNING with INFO version message - Add REINDEX notice to upgrade scripts (segment format V3→V4) - Add 0.5.1 to upgrade test matrix - Update compatibility matrix in RELEASING.md - Update expected test output for new version message
0.6.0 is still pre-GA, so keep the WARNING message on extension creation to match previous prerelease behavior.
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
1 participant
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
bm25_force_mergefunctionBreaking changes
Segment format changed from V3 (uint32 offsets) to V4 (uint64 offsets).
Users upgrading from 0.5.x must run
REINDEXon all bm25 indexes afterALTER EXTENSION pg_textsearch UPDATE.Testing
make test— 49/49 passmake format-check— pass