ClickHouse Managed Postgres

Let's pause a little bit because I think what's interesting here is that we have a couple of Postgres companies acquired last year by analytical database companies, right? Snowflake and Databricks.

And in this case, Postgres and Clickhouse, I think it's a...

Great, interesting combination of two very open source projects originally.

The majority of things are open source.

And I see it in our customers.

It's often the case Postgres is for LTP and Clickhouse is for analytics.

So I guess this is where you manage to be with your plumbing business, right? With PeerDB.

I love the way you call it, plumbing business.

Yeah, yeah.

This is where we're all in, but you literally called it PureDB because it's about pipes and so on.

Click pipes also, like it's plumbing, right? What

is it? It is

plumbing.

It should not be leaking and so on, right?

Yeah, absolutely.

So this is a great combination of two, I think, great open source projects.

And you entered ClickHouse with plumbing, as I said.

And then I want to understand the idea that ClickHouse needs their own Postgres better, because originally I know Milovidov chose MySQL protocol originally.

I know now it's like partially supported Postgres protocol, but...

Somehow, ClickHouse was a good fit for those who use Postgres, but it was not completely relative to Postgres.

It's not relative.

It was very far originally.

No, I think that totally makes sense, Nick.

So the reason why we started Manage Postgres within ClickHouse is, if you look at it, right, currently there are tens of thousands of companies who use Postgres and ClickHouse together.

Postgres powers transactions, ClickHouse powers analytics, and Basically, they are using the right tool for the right job.