Skip to main content

What's new in ArpePGSQL

Feature-oriented release highlights for ArpePGSQL — the pure-native PostgreSQL ADBC driver that speaks the Frontend/Backend (FEBE) protocol v3 directly and streams Apache Arrow end-to-end (no libpq).

Get it in one line — see the install guide:

curl -fsSL https://raw.githubusercontent.com/arpe-io/adbc-drivers/main/install.sh \
  | sh -s -- arpepgsql --license ./arpeio_adbc.lic

Npgsql connection strings — October 2026 (v0.4.6)​

Npgsql keywords (Host, Port, SSL Mode, …) and host:port.

PostgreSQL client environment — October 2026 (v0.4.5)​

PGUSER, PGPASSWORD, ~/.pgpass and PGSSLROOTCERT are read.

ADBC conformance catch-up — October 2026 (v0.4.4)​

BindStream for parameterized queries.

Lossless NUMERIC by default — October 2026 (v0.4.3)​

New options numeric_format and numeric_special; a NaN in a decimal column now fails the read by default.

PostgreSQL-wire-compatible engines — September 2026 (v0.4.2)​

New option copy_format.

ArrowFEBE renamed ArpePGSQL — September 2026 (v0.4.1)​

Rebrand only; no behaviour change.

RHEL 8 support, leaner defaults & binary hardening — September 2026 (v0.4.0)​

The shipped Linux driver now runs on RHEL 8 / Rocky 8 and every newer distro out of the box (self-contained, TLS built in). The default read batch size drops from 100,000 to 32,000 rows for a lighter memory footprint.

Hardened release binaries — August 2026 (v0.3.8)​

The published Linux and Windows binaries are stripped of internal symbols. A supply-chain hardening pass with no runtime cost.

Refuse plaintext passwords & a safer cancel — August 2026 (v0.3.7)​

A new opt-in require_password_encryption option makes the driver refuse to send a cleartext or MD5 password over a transport that is not TLS-encrypted, closing a MITM downgrade (off by default, libpq-compatible). This release also fixes a cross-thread use-after-free in cancel and completes the ADBC 1.1.0 statistics surface with GetStatisticNames.

Portable connection URIs — August 2026 (v0.3.6)​

Connect with a standard libpq-style URI on the ADBC uri option — postgresql://…, postgres://…, or the branded arpepgsql://… — so strings copied from psql or a DATABASE_URL just work. See Connection → URI.

A standalone driver you install by name — August 2026 (v0.3.5)​

ArpePGSQL is now an independently installable ADBC driver: one-line install of a checksum-verified binary, load by name (driver="arpepgsql"), and a reworked COPY-binary encoder that made bulk ingest ~2.2× faster.

Shared family environment & always-on licence — August 2026 (v0.3.6)​

Environment variables moved to the shared ARPEIO_ADBC_* prefix, so one variable configures every Arpeio driver. The licence check is now always enforced.

Real query cancellation & a self-contained Windows DLL — June 2026 (v0.2.2)​

AdbcConnectionCancel / AdbcStatementCancel now abort an in-flight query via an out-of-band PostgreSQL CancelRequest, and the Windows driver ships as a self-contained DLL.

Integrated authentication — June 2026 (v0.2.0)​

Trusted/integrated auth with no password, through Windows SSPI (Windows driver only). Mutual authentication is always enforced. See Authentication.

PostGIS geospatial — June 2026 (v0.2.4)​

PostGIS geometry / geography columns read as interoperable GeoArrow / WKB — their EWKB wire bytes pass straight through as Arrow binary, with no server-side ST_AsBinary round-trip, and a clean no-op when PostGIS is absent. See Data types → Geospatial.

SCRAM channel binding — June 2026 (v0.1.4)​

SCRAM-SHA-256-PLUS channel binding (channel_binding=require) binds the auth exchange to the server certificate over TLS, defeating a MITM that proxies the SASL flow — even without full certificate verification.

Native NUMERIC, interval & richer types — June 2026 (v0.1.5)​

numeric decodes straight from PostgreSQL's binary layout into decimal128/decimal256 with no string detour — the headline differentiator over the upstream Apache PostgreSQL driver — plus native round-trips for interval, json/jsonb, inet/cidr/macaddr, and bit/varbit. See Data types.

The native FEBE engine — foundational (v0.1.0)​

From the start, ArpePGSQL speaks the PostgreSQL v3 Frontend/Backend protocol directly over TCP/TLS — no libpq, no ODBC. A COPY-binary fast path (~1.70× the upstream Apache PostgreSQL driver on a TPC-H SF10 lineitem extract), native bulk ingest via COPY FROM STDIN, and the full ADBC 1.1.0 surface.

To report an issue or request a licence, contact sales@arpe.io or visit https://www.arpe.io.