handlers: fix response encoding format #15
Merged
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.
According to the official wire protocol documentation1:
However, for the binary protocol the situation is more complicated, as this is determined by the
Bind2 command3:Given the above infromation, this aligns the implementation here with the
sqlliteandduckdbexamples from thepgwirerepository.To see why the current state is an issue, try running
SELECT 1::int4from a Rust crate that usesrust-postgres. Using the example from this gist:cargo run --example pg_client -- query "SELECT 1::int8"Without the fixes I get:
with the fixes:
Footnotes
https://www.postgresql.org/docs/current/protocol-flow.html#PROTOCOL-FLOW-SIMPLE-QUERY ↩
https://www.postgresql.org/docs/current/protocol-message-formats.html#PROTOCOL-MESSAGE-FORMATS-BIND ↩
https://www.postgresql.org/docs/current/protocol-flow.html#PROTOCOL-FLOW-EXT-QUERY ↩