docs: link ArcadeDB's published account of the four protocol findings - #140
Merged
Merged
Conversation
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
1 participant
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.
ArcadeDB published a piece on 2026-09-21 covering the four PostgreSQL-wire findings this project's testing produced (#7178, #7188, #7815 and #8090), the two Arrow routes and the language benchmark:
https://arcadedb.com/blog/arcadedb-apache-arrow-adbc-postgresql-wire/
It carries a byline, the throughput table with its full methodology and the ratios-not-absolutes caveat verbatim, and credits #7815 to this project as a pull request.
Linked from three places so a reader lands on it from wherever they start: the ArcadeDB compatibility entry (which is what the matrix row shows), the #8090 tracker row, and both ArcadeDB notes.