Exasol Postgres Proxy
A -wire-compatible proxy that lets PostgreSQL clients and query 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 ; behind the proxy it translates queries and metadata access into Exasol-compatible behavior.
The practical target is 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 . 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.
Most of the code is translation rules and catalog compatibility views, wrapped in the operational parts a proxy needs to be run rather than demonstrated: TLS, streaming, admin routes, and packaging.
Design choices
The documentation covers translation logs and schema behavior as prominently as connection setup. A failing proxy is otherwise very hard to reason about, because the client reports a PostgreSQL error for something that went wrong two translations away.
Current state
Active. Recent work has been on large queries, how fast the first row arrives, and the admin .