News for hackers. Stuff that matters.

A comment on Migrating to Postgres. Parent comment

Re:Migrating to Postgres by moonikakiss on Wednesday May 14, 2025 @10:17PM (#43991213)
exactly. we take the CDC output / logical decoding from your OLTP tables and write into a columnar format with <s freshness.

We had to design this columnstore to be 'operational' so it can keep up with changing oltp tables (updates/deletes).

You'll be able to deploy Mooncake as a read-replica regardless of where your Postgres is. Keep the write path unchanged, and query columnar tables from us.

--- v0.2 will be released in preview in ~a couple weeks. stay tuned!

[ Parent | on HN ]
Re:Migrating to Postgres by I_am_tiberius on Wednesday May 14, 2025 @10:36PM (#43991284)
Ah, I see. So there's a replication process similar to ClickHouse's MaterializedPostgres. Ideally, there would be functionality allowing a columnstore query to wait until all writes to the OLTP tables — up to the query's execution time — are available. This would make the system truly Postgres-native and address issues that no other system currently solves.
[ Parent | on HN ]
Re:Migrating to Postgres by moonikakiss on Wednesday May 14, 2025 @11:19PM (#43991505)
yep exactly. we can wait for replay LSN. So you're only reading once all writes to OLTP are complete.
[ Parent | on HN ]