feat: query parser backend without protobuf in pg_query #699
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.
We forked pg_query and replaced protobuf (de)serialization with native C/Rust bindings.
This results in the following performance improvements:
pg_benchis reporting a 25% improvement in benchmarks using the simple protocol, which we don't cache. This is great for clients that don't support or use prepared statements (e.g. Rails!).This is configurable with the new
query_parser_enginesetting:While we continue to test this, we'll be using the old protobuf-based paths by default. This PR therefore won't affect any current deployments and adoption is completely optional.
Things we need to optimize:
Misc
Upgraded rand to 0.9.2.