Materialize into Apache Arrow through ADBC, using psqlodbc 16 (adbcBridge 0.1.0)

[singhpratech]

adbcBridge is a small Apache-2.0 ADBC driver written in C11 that loads an ODBC driver and exposes it through the Arrow ADBC C ABI: block-cursor reads straight into Arrow record batches, bulk ingest, metadata, partitioned parallel reads. I ran Materialize through it as one of 46 databases in a single compatibility workload and wanted to share the entry here.

What was verified (Materialize 26.38; driver: psqlodbc 16)

• Linux: PASS
• macOS arm64: PASS (PostgreSQL wire 9.5.0)
• Windows x64: PASS (Materialize v26.38.2)

What the compatibility entry records: PostgreSQL SQL layer, so no driver quirks — but no SAVEPOINT, so the entry sets psqlodbc's Protocol=7.4-0 to stop the driver wrapping the second batch of a large ingest in one; its single 39-digit NUMERIC is wider than an Arrow decimal128, so decimals read back as exact strings; the entry also ingests into and reads back an incrementally maintained MATERIALIZED VIEW; ingest 23.6k rows/s, fetch 322k rows/s. Full entry: docs/COMPATIBILITY.md.

The postgresql ADBC driver may also work with Materialize over its wire protocol; this path goes through psqlodbc and records exactly what it needed, so it is a second, documented route rather than a replacement.

Trying it (Python; Rust, Go, Java and C# are on the docs site):

pip install adbcbridge

import adbcbridge
with adbcbridge.connect(uri="Driver=PostgreSQL Unicode;Server=127.0.0.1;Port=6875;Database=materialize;Uid=materialize;Protocol=7.4-0") as conn:
    with conn.cursor() as cur:
        cur.execute("SELECT * FROM my_view")
        table = cur.fetch_arrow_table()   # a pyarrow.Table

Links: repository · docs · upstream notes · PyPI

It is a 0.1.0. If the entry says something wrong about Materialize, or you run a version or driver I didn't, an issue on the repository with the details is the most useful thing you could send.

[singhpratech]

A follow-up with one new measurement. On 2026-09-05 I ran the same seven-step ADBC workload (connect, SELECT 1, DDL + inserts + read, 1,000-row adbc_ingest, GetTableSchema, GetObjects, read back) through the Apache Arrow native PostgreSQL ADBC driver (1.12.0) and through adbcBridge over psqlodbc, against the Materialize image in the matrix.

Native driver: stops at connect. Its type-resolver bootstrap, SELECT oid, typname, typreceive, typbasetype, typrelid, typarray FROM pg_catalog.pg_type WHERE (typreceive != 0 OR typsend != 0) …, is rejected, so no connection is ever established. That is the native driver assuming a full pg_catalog, not a Materialize defect.
ODBC path: all seven steps pass, including ingest into a table feeding a materialized view.

The full table for all 28 PostgreSQL-wire and MySQL-wire databases, with each native driver's first error, is here: https://adbcbridge.org/notes/native-adbc-drivers-on-wire-compatible-databases/

One thing from that run that affects nobody on Materialize but is worth stating: adbcBridge's default auto-delegation to the native driver falls back to ODBC correctly here, because the native driver fails at connect. On servers where it connects and then fails (CockroachDB, CrateDB, YDB) it did not, and that is fixed in singhpratech/adbcbridge#74 for 0.1.1.