CacheDB 1.9 compatibility
Support depends on the protocol path, not just the database name.
CacheDB supports native relays for PostgreSQL and MySQL, and PostgreSQL-front-end translation for selected enterprise backends. Each path has distinct requirements and limits.
Compatibility matrix
Choose and test the exact path you intend to operate.
All translation paths need workload-specific validation for SQL semantics, data types, prepared statements, transactions, error behavior, and network design.
| Database | Client protocol | Proxy path | Availability / requirements |
|---|---|---|---|
| PostgreSQL | PostgreSQL | Native transparent relay | Recommended PostgreSQL deployment; auth is relayed. |
| MySQL | MySQL | Native packet relay | Native client path; compression and TLS capabilities are not offered by the proxy. |
| PostgreSQL | PostgreSQL | Backend-connection path | Requires standard_conforming_strings = on. |
| Oracle | PostgreSQL | Translation | Operator supplies the licensed Oracle driver. |
| SQL Server | PostgreSQL | Translation | Test SQL/type semantics; certificate validation is not enforced in 1.9. |
| IBM DB2 | PostgreSQL | Translation | Operator supplies the licensed DB2 driver. |
Evaluation requirements
Validate behavior with the real client workload.
Use the actual client driver and protocol. Include prepared statements, multi-statement behavior, transaction boundaries, data types, result sizes, and error handling in the evaluation plan. Start in transparent mode to observe the path before introducing result reuse.
Oracle and DB2 drivers are not distributed by Houdata. They remain licensed, operator-supplied dependencies in bare-metal and container deployments.
Read container driver requirementsDeployment limitation
Protocol support does not make the proxy a TLS endpoint.
Current CacheDB 1.9 transport restrictions apply to every supported path. Place the components on a trusted private network or provide encryption at the deployment layer.
Review security boundariesCompatibility discussion
Bring the database and driver details.
We can map the intended application protocol, backend, driver dependencies, and operational constraints to the appropriate CacheDB path.