ArcadeDB - one Query message, several statements, and the fix sent upstream so psqlodbc 16 connects again
Update, 2026-11-11: fixed on main, ships in ArcadeDB 26.12.1. The maintainer merged a fix of his own the same
evening, ArcadeData/arcadedb#11485. It takes the same shape as
the one described below, built on the module's own lexer: each statement of the message runs in turn and gets its own
result, the statements share one implicit transaction, and one ReadyForQuery ends the message. It also refuses a
prepared statement holding several statements with PostgreSQL's own message. Verified here on the 26.12.1-SNAPSHOT
image built from that merge commit (601600ee): psqlodbc 16 connects with a plain connection string, the three-statement
setup is answered SET, SET, one row, and the September probes pass through the driver and through adbcBridge.
Update, 2026-11-12: the follow-up fix from here is merged too. One case was left on main after #11485: a
multi-statement message that failed on a follower of a three-node cluster kept its write on every server, because the
follower forwarded each write to the leader, where it committed on its own. The pull request described in this note,
#11484, was reduced to that case, one line that marks the implicit
transaction the way BEGIN does plus a three-node test, and merged on 2026-11-11. Both changes ship in ArcadeDB 26.12.1.
The 26.11.1 release retest confirmed four fixes and turned up one new
finding: psqlodbc 16, the build Debian and Ubuntu ship as odbc-postgresql, cannot open a connection to ArcadeDB
26.10.1, 26.10.2 or 26.11.1. On 2026-11-10 it went upstream as a report,
ArcadeData/arcadedb#11483, and as a fix,
ArcadeData/arcadedb#11484.
What the driver sends
psqlodbc 16 sets up each connection with one simple-query message:
SET DateStyle = 'ISO';SET extra_float_digits = 2;show transaction_isolation
Three statements, one message. The PostgreSQL protocol allows that: the server answers each statement in turn and
sends a single ReadyForQuery at the end. ArcadeDB handed the whole text to one statement matcher, where it read as
a single SET nobody could parse. Until 26.9.1 that was answered leniently and the connection went ahead. Since
26.10.1 an unparseable SET is a syntax error, which is the right answer for a real one, and the connection is
refused:
[42601] ERROR: Error on executing query: syntax error in
"SET DateStyle = 'ISO';SET extra_float_digits = 2;show transaction_isolation"
psqlodbc 18 asks SHOW DateStyle; on its own first and connects. adbcBridge's default delegation hands a
psqlodbc data source to the native PostgreSQL driver, so it connects too; the refusal shows with delegation off, which
is how the compatibility matrix runs.
What the fix does
The pull request teaches the simple-query path what PostgreSQL does with such a message:
- The text is divided on its top-level semicolons. A
;inside a quoted literal, a quoted identifier, a dollar-quoted body or a comment is text, and a trailing or doubled;adds no statement. - Each statement gets its own answer, the first error skips the rest, and one
ReadyForQueryends the message. - The statements share one implicit transaction. A failure takes back what the earlier statements wrote. A
BEGINamong them leaves an explicit block open for the client to end. - A single statement takes the path it always took, and a text that opens with a
{language}marker, such as an ArcadeDB{sqlscript}, is left whole.
How it was checked
| Check | Result |
|---|---|
| New wire-level test on ArcadeDB main, without the fix | 5 of 6 cases fail |
| Same test with the fix | 6 of 6 pass |
| psqlodbc 16's connect string | SET, SET, the SHOW row, one ReadyForQuery |
| The whole PostgreSQL-wire module with the fix | 988 unit tests and 603 integration tests pass |
The test speaks the wire protocol directly, because JDBC splits such a text on the client and never sends it as one message.
Until it ships
Use psqlodbc 18 with ArcadeDB 26.10.1 and later, or leave adbcBridge's delegation on its default. Both are recorded in the compatibility matrix and in UPSTREAM.md.