Repository navigation
Fix column state leaking between COPY loads (VTA-118540) - #26
Merged
Conversation
Collaborator
Author
|
VTA-118540-Pre-and-Post-Fix-Test-Results.docx UT details attahced. |
mkottakota1
requested changes
Oct 8, 2026
mkottakota1
left a comment
mkottakota1
left a comment
Collaborator
There was a problem hiding this comment.
Could you add a new test case covering this fix scenario?
SandeepDave2
force-pushed
the
VTA-118540-Fix_COPY_not_working_while_loading_data_from_different_source_tables_from_same_VSQL_session
branch
from
October 9, 2026 04:57
b7c742f to
d222aa6
Compare
Collaborator
Author
Done. |
mkottakota1
approved these changes
Oct 9, 2026
mkottakota1
left a comment
mkottakota1
left a comment
Collaborator
There was a problem hiding this comment.
Sandeep has added the new test case which covers the regression. Code changes are looking good
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.
Fix:
Successive COPY loads with different column counts could reuse stale column metadata, causing an invalid setter exception.
Make the column count and mapping instance-owned, initialize them for each load, and validate mapping sizes/indexes before binding columns.
Preserve external-table projection and NULL handling.
Addresses VTA-118540.
Verification:
Manually tested in fenced mode on Vertica 26.4.0 with PostgreSQL 15: