Skip to content

Actually handle more than 4 result columns from IDENTIFY_SYSTEM#74

Merged
jackc merged 2 commits intojackc:masterfrom
gadget-inc:sc/fix-handle-more-than-4-result-columns
Mar 31, 2025
Merged

Actually handle more than 4 result columns from IDENTIFY_SYSTEM#74
jackc merged 2 commits intojackc:masterfrom
gadget-inc:sc/fix-handle-more-than-4-result-columns

Conversation

@scott-rc
Copy link
Copy Markdown
Contributor

I'm sorry, this is a follow up to #73 -- I accidentally made ParseCreateReplicationSlot handle more than 4 result columns rather than ParseIdentifySystem 🤦

This PR reverts my original commit in #73 and makes the actual change I meant to make.

@sammy-hughes
Copy link
Copy Markdown

sammy-hughes commented Mar 31, 2025

This PR appears to resolve an issue we encountered recently, also using AlloyDB. The added column is "authtoken", and is not relevant to our workflow. This field-inclusion does not appear to be documented anywhere, either in AlloyDB docs or the google/alloydbomni image.

The google/alloydbomni image appears to not make this same field-inclusion, which further confirms that this is not meaningful for replication consumers.

@sammy-hughes
Copy link
Copy Markdown

I added Issue #75 to explain the impact of the issue which this PR resolves.

@jackc jackc merged commit 51ad596 into jackc:master Mar 31, 2025
10 checks passed
@scott-rc scott-rc changed the title Revert "Handle more than 4 result columns from IDENTIFY_SYSTEM" Actually handle more than 4 result columns from IDENTIFY_SYSTEM Mar 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants