Exasol Postgres Proxy
A PostgreSQL-wire-compatible proxy that lets PostgreSQL clients and Qlik Cloud query Exasol without requiring a native Exasol driver on the client side.
What it does
ExaProxy sits between PostgreSQL-compatible clients and Exasol. To the client it speaks PostgreSQL wire protocol; behind the proxy it translates queries and metadata access into Exasol-compatible behavior.
The practical target is Qlik Cloud and diagnostic tools such as DBeaver, where PostgreSQL connectivity is easy to configure but native Exasol drivers are not always available.
Technical problem
The proxy has to do more than forward SQL. PostgreSQL clients ask catalog questions, expect certain type metadata, and rely on protocol behavior that Exasol does not provide directly. ExaProxy implements enough compatibility to make those clients productive without pretending to be a full PostgreSQL database.
The codebase includes translation rules, catalog compatibility views, streaming behavior, TLS setup, admin routes, and operational packaging.
Design choices
The project keeps client compatibility and operational diagnosis visible. Documentation covers connection setup, translation logs, schema behavior, and streaming tradeoffs, which matters because proxy failures are otherwise hard to reason about.
Current state
Active. Current work focuses on large-query behavior, first-row timing, schema compatibility, and the administrative UI.