Repository navigation
Conversation
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
This adds the match operator
@@of text search fortsvectorandtsquery, asts_match_vqandTS_executeoftsvector_op.chave it. The functions that need a text search configuration, such asto_tsvector, are not in this change.Changes
rupg-funchas the new moduletsmatch, withts_match_vqandts_match_qv. The operators@@and@@@use these functions in both argument orders.cat:*matches each lexeme that starts with the prefix. Under<N>, the positions of all these lexemes are merged.<N>followsTS_phrase_execute. It has the rules of PostgreSQL for!,&and|under<N>, and the width of a match.<N>gives the result "maybe", asTS_MAYBEdoes. At the top of the query,<N>with this result does not match.WordEntryPosdoes. Thus a large<N>gives the same result as PostgreSQL.Tests
ts_matchis the output of PostgreSQL 19 for the same script in a new database. It has weights, prefixes,!,&and|inside and outside<N>, positions near the limit, vectors with no positions,GROUP BYon a match,@@@and a query with parameters.