Database · PostgreSQL wire

YugabyteDB into Apache Arrow with ADBC

YugabyteDB 2026.1 (YSQL), read and written through adbcBridge — the ADBC driver that loads the database's ODBC driver — verified on Linux, macOS arm64 and Windows x64. Everything below is the compatibility matrix's record for this row.

Status

Linux✓ pass

PASS

macOS arm64✓ pass

PASS (YugabyteDB, PostgreSQL wire 15.12, arm64)

Windows x64✓ pass

PASS (YugabyteDB 2026.1.1.1, PostgreSQL wire 15.12; psqlodbc 18.00.0002)

Driver and connection string

ODBC driver: psqlodbc 16 (PG wire)
Wire: PostgreSQL wire
adbcBridge: 0.1.1 (release)

The connection string the matrix used, as the connection strings reference records it (PostgreSQL wire); {drv} is the driver library or its name from odbcinst.ini, and the host, port and credentials are the test server's.

Driver={drv};Server=127.0.0.1;Port=15433;Database=yugabyte;Uid=yugabyte;

Python

import adbcbridge

# {drv}: the ODBC driver library (path), or its name from odbcinst.ini
conn = adbcbridge.connect(uri="Driver={drv};Server=127.0.0.1;Port=15433;Database=yugabyte;Uid=yugabyte;")
with conn.cursor() as cur:
    cur.execute("SELECT * FROM my_table")
    table = cur.fetch_arrow_table()      # pyarrow.Table

Polars and pandas

import polars as pl, pandas as pd

df = pl.read_database("SELECT * FROM my_table", connection=conn)   # Polars, Arrow-native
pdf = pd.read_sql("SELECT * FROM my_table", conn)                   # pandas 2.2+, ADBC connection

pip install adbcbridge brings the driver library; the YugabyteDB ODBC driver is installed the way its vendor documents, then named in Driver=. Rust, Go, C# and Java use the same connection string through their ADBC driver managers — see the docs.

What the matrix recorded

no quirks; YSQL is PostgreSQL 15, and its internal row id is a system column so GetObjects is unaffected; version() carries -YB-, so the PostgreSQL array-ingest form stays off (verified); no ctid (0A000), and its default PRIMARY KEY (id) is hash-partitioned, so partitioned reads split on yb_hash_code() — 2.6x over a single connection, and 2.2x better than a key range, which YugabyteDB would run as a Seq Scan with a Storage Filter.

What this stack needed

Against the native driver it reaches 1.18–1.22x at 4 M rows, i.e. on the 1.2x bar rather than over it, and 0.94x at 1 M: the server is the bottleneck there, not psqlodbc

Native ADBC driver, compared

YugabyteDB speaks the PostgreSQL wire protocol, so Apache Arrow's native PostgreSQL ADBC driver (adbc-driver-postgresql 1.12.0) can be pointed at it too. On 2026-09-05 the same seven-step ADBC workload (connect, SELECT 1, DDL and inserts and a read, a 1,000-row adbc_ingest, table schema, catalog listing, read back) ran through both:

Path	Result	First error
Native ADBC driver	✓ all seven steps
adbcBridge over ODBC	✓ all seven steps

Where the native driver stops it is by design of that driver, not a defect of YugabyteDB; the full table for all 28 wire-compatible databases, with each first error, is in the note.