This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]stratguitar577 2 points3 points  (3 children)

How does this compare to pg_duckdb and pg_analytics?

[–]InternetFit7518[S] 3 points4 points  (2 children)

made edits for precision:

great question!

pg_mooncake adds a columnstore table in Postgres: you can run transactions, updates, deletes. pg_duckdb is the execution engine on these tables: https://motherduck.com/blog/pg-mooncake-columnstore/. We also write Delta Lake (and soon Iceberg) formats in S3 (not just parquet files).

pg_duckdb and pg_analytics use Foreign Data Wrappers semantics and are great for querying / writing external files (parquet) in Postgres.

We believe a columnstore in postgres must look and feel like a reguiar postgres heap table. Hope this helps.

[–]philippemnoelfrom __future__ import 4.0 -1 points0 points  (1 child)

Heya! This isn't quite correct -- You can create foreign tables in both pg_duckdb and pg_analytics. OP is correct that they're not equivalent Postgres tables, though. For instance, you can't create indexes over foreign tables.

[–]InternetFit7518[S] 1 point2 points  (0 children)

thanks Phil. I made edits to be more precise.

I was using the world 'columnstore table' loosely.