Convert DuckDB VARCHAR[] to PG TEXT[] to Prevent Type Mismatch #979
+18
−11
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
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.
DuckDB’s VARCHAR type is mapped to PostgreSQL TEXT, but its VARCHAR[] arrays were previously mapped to PostgreSQL VARCHAR[]. This inconsistency causes a type mismatch on the Postgres side during statistics analysis, triggering an assertion in
array_typeanalyze.c::compute_array_stats:This PR standardizes the behavior by converting DuckDB VARCHAR[] to PostgreSQL TEXT[].
A sample dataset is included to reproduce the original failure.