Postgres and ClickHouse can share tables. EnterpriseDB wants one set of rules to govern them.
If you have built anything that needs both a system of record and fast analytics, you know the shape of The post Postgres and ClickHouse can share tables. EnterpriseDB wants one set of rules to govern them. appeared first on The New Stack .
Postgres and ClickHouse software can share tables, and EnterpriseDB wants a unified set of rules to govern them. Both engines excel in their respective domains, but the challenge lies in the gap between them.
The first pain point is the complexity of the Change Data Capture (CDC) job, which involves multiple moving parts between a committed Postgres transaction and the same row being queryable in ClickHouse software. This includes a replication slot, a connector with its own failure modes, a message broker, a sink, a dedup strategy, monitoring, and more. None of this code belongs to the product, and it contributes to the on-call rota.
The second pain point is the need for agents to reason over stale data. Developers often write code to query Postgres for current state and ClickHouse software for trends, then stitch the two together in the application. This integration layer is prone to bugs, as it is where errors often occur.
The third pain point is running the stack twice. Each row-level rule, masked column, and policy exists in both Postgres and ClickHouse software, leading to drift and the need for updates to be made in both systems. This results in duplicate infrastructure, permission models, and support contracts, creating vendor lock-in.
EnterpriseDB has acquired Altinity, the company behind Altinity Stable Builds, the Altinity Kubernetes Operator, and Altinity.Cloud. This acquisition aims to create one shared layer for Postgres, WarehousePG, and ClickHouse software, with a unified governance model and control plane. This will reduce the number of hops, eliminate bespoke reconciliation code, and stop the CDC job from being owned by the product team.
Additionally, EDB Postgres AI will pair a sovereign multi-model data layer with an agentic runtime and governance enforced at the data layer. This will allow agents to ask for business context and receive the record and analysis from a single system, rather than having to orchestrate two databases and a queue. One governance model will be defined and enforced across all three engines, simplifying permissions management.
Finally, Altinity's expertise in running ClickHouse software in production will be integrated, allowing the control plane to run Postgres and ClickHouse software on the customer's preferred cloud, on-premises, or fully managed.
Rewritten by urgent.news; may contain errors — check the original.