Fix bm25query varlena detoasting for binary I/O and scoring #123
+127
−14
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
tpquery_out,tpquery_send,bm25_text_bm25query_score, andtpquery_eqnow properly detoast varlena argumentstpquery_sendto usepq_begintypsend()for proper binary protocol formattingtpquery_recvto usepq_getmsgbyte()for version fieldBackground
When Postgres stores small varlena values, it may use a 1-byte header instead of the standard 4-byte header. Functions using
PG_GETARG_POINTERinstead ofPG_DETOAST_DATUMwould access struct fields at incorrect offsets, causing data corruption.This manifested as:
tpquery_outTesting
binary_io.sqltest that verifies COPY BINARY round-trip for bm25query type