ArpePGSQL — Compatibility
Which PostgreSQL versions, PostgreSQL-compatible services, and client platforms ArpePGSQL is known to work with. Three support states are used across the Arpeio driver family:
| State | Meaning |
|---|---|
| ✅ Validated | Tested directly against this target before release. |
| 🟢 Supported | Expected to work and covered by the same protocol surface, but not run continuously. Report issues and they will be treated as bugs. |
| 🟡 Not yet validated | Should be compatible on protocol grounds, but unverified. No promise yet. |
ArpePGSQL speaks the PostgreSQL Frontend/Backend (FEBE) protocol v3 natively over TCP (+ optional TLS). Any server that negotiates FEBE v3 is a candidate; the mapping details are in Data types.
PostgreSQL (on-premises / IaaS)
| Version | State | Notes |
|---|---|---|
| PostgreSQL 17 | ✅ Validated | |
| PostgreSQL 16 | ✅ Validated | |
| PostgreSQL 15 | ✅ Validated | |
| PostgreSQL 12 | ✅ Validated | The stated floor. |
| PostgreSQL 14 / 13 | 🟢 Supported | Same FEBE v3 surface as the validated versions. |
| PostgreSQL ≤ 11 | 🟡 Not yet validated | Older but still FEBE v3 — expected to work for core types; untested and out of support upstream. |
The stated floor is PostgreSQL 12+. Versions 12 / 15 / 16 / 17 are
tested end to end: SCRAM, MD5 and cleartext authentication, TLS
require/verify-full, the ADBC conformance suite, and the full data-type
mapping.
PostgreSQL-compatible services & forks
These speak the PostgreSQL wire protocol but are not tested. They are expected to work for the core surface on protocol grounds only — treat them as unverified until you have run your own workload.
| Service | State | Notes |
|---|---|---|
| Amazon Aurora PostgreSQL | 🟡 Not yet validated | PostgreSQL-compatible; untested. |
| Amazon Redshift | 🟡 Not yet validated | PostgreSQL-protocol-compatible, but a different type/feature surface; unverified. |
| Greenplum | 🟡 Not yet validated | PostgreSQL-derived MPP; unverified. |
| CockroachDB | 🟡 Not yet validated | PostgreSQL wire-compatible, distinct engine; unverified. |
| YugabyteDB | 🟡 Not yet validated | PostgreSQL wire-compatible; unverified. |
Managed stock-PostgreSQL services (Amazon RDS for PostgreSQL, Azure Database
for PostgreSQL, Google Cloud SQL for PostgreSQL, Supabase, Neon, …) run genuine
PostgreSQL and fall under the version rows above; require TLS with
sslmode=verify-full for those endpoints.
Authentication methods
| Method | Platform | State |
|---|---|---|
| SCRAM-SHA-256 (password) | all | ✅ Validated |
| SCRAM-SHA-256-PLUS (channel binding over TLS) | all (TLS) | ✅ Validated |
| MD5 password | all | ✅ Validated |
| Cleartext password | all | ✅ Validated |
| Integrated — Windows SSPI (Negotiate) | Windows client only | 🟢 Supported |
Integrated (trusted) authentication is not available with the Linux driver. See Authentication and Connection → Authentication for setup.
Client platforms
| Platform | State | Notes |
|---|---|---|
| Linux x64 | ✅ Validated | Self-contained .so (TLS built in); runs on RHEL 8 / Rocky 8 and newer distributions. Password-family authentication only. |
| Windows x64 | 🟢 Supported | Self-contained DLL (TLS built in; no OpenSSL or Visual C++ runtime DLLs needed). Adds integrated authentication via SSPI. |
| macOS | — | No released binary. |
ADBC conformance
ArpePGSQL passes the upstream ADBC driver validation suite (324 passed / 4 skipped / 25 expected failures / 0 failed). Every expected failure is a genuine PostgreSQL limitation, not a driver defect — most notably Arrow nanosecond temporal precision (PostgreSQL stores microseconds) and a few unsupported bind inputs.
See also
- Connection — connecting to each of the above
- Data types — the PostgreSQL ↔ Arrow type mapping
- Troubleshooting — when a supported target does not connect