Repository navigation
fix(net): proper parse for -c inside startup parameters - #1905
Merged
Merged
Conversation
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
jkaczman
approved these changes
Oct 27, 2026
jkaczman
left a comment
Contributor
There was a problem hiding this comment.
LGTM, other than maybe adding a short description of the motivation and what this changes
Contributor
|
Metal bench passed. All 150 measures within bounds.
Counters per txn
Microbench: all 135 measures within bounds.
Logslb, microbench, pooler, sharding-w2, sharding-w8, verdict.json |
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 the parsing logic for the startup options.
Previously, the parsing was splitting by
-cand=without considering escaping and these symbols appearing inside the params, so the-c pgdog.sharding_key=270b77fd-c30e-…becomes["", " pgdog.sharding_key=270b77fd", "30e-…"]instead of proper value parsing.Make the logic more like in PG: split by whitespaces, considering escapes.
Also, I removed the special
+sign treatment in string from #976 - this is not how PG parses the string and this introduce so many edge cases, while it was never a proper solution for the issue at the first place.