moonikakiss

6 ms·

31.
Everything is sales(writing.nikunjk.com)
1 points by moonikakiss 2y ago|0 comments
32.
WTF are AWS S3 tables?(mooncake.dev)
2 points by moonikakiss 2y ago|0 comments
33.
What does Analytics in Postgres even mean?(mooncake.dev)
4 points by moonikakiss 2y ago|0 comments
34.
by moonikakiss 2y ago
This is an interesting workload. We've heard similar pains for fast filtering on many large column tables. For this workload, having a columnstore version of your table will help. DM us: https://join.slack.com/t/mo
35.
by moonikakiss 2y ago
try us on Neon Postgres https://neon.tech/docs/extensions/pg_mooncake . It should be fairly trivial to get started
36.
by moonikakiss 2y ago
In v0.1, we have a dependency on pg_duckdb which does not support citus ( https://github.com/duckdb/pg_duckdb/issues/444 ). With what we're working in v0.2, we re-architecture some of our dependencies ther
37.
by moonikakiss 2y ago
Both add the DuckDB extension. But the use-case is slightly different: 1. pg_duckdb is great for querying existing columnar files (parquet) in Postgres. 2. Our focus is on helping you write and query your existing Postgres table into a colu
38.
by moonikakiss 2y ago
In v0.2, this is exactly what we're building. Keep your OLTP as it. Deploy Mooncake with logical replication into columnstore tables, and get DuckDB like perf. A big part of this is not replacing your OLTP.
39.
by moonikakiss 2y ago
oh yeah. We're baking 0.2. Extremely excited about the small-writes. Today, each insert will create a new parquet file. This will be fixed in v0.2. Stay tuned, we will have some announcements here coming soon.
40.
by moonikakiss 2y ago
One thing I forgot to mention. We're actually faster than DuckDB on parquet. We implemented segment elimination based on parquet metadata. We blogged about this: https://www.mooncake.dev/blog/duckdb-parquet
41.
by moonikakiss 2y ago
oh and I totally forgot. pg_mooncake is actually faster than DuckDB on parquet. We implement segment-elimination to do so. We even blogged about it: https://www.mooncake.dev/blog/duckdb-parquet
42.
by moonikakiss 2y ago
Well, pg_mooncake is a Postgres extension. So it's really just Postgres :) We embed DuckDB in our extension as the vectorized execution engine on columnstore tables. Why rebuild a vectorized execution, when DuckDB has a lot of GREAT pr
43.
by moonikakiss 2y ago
I know! It's crazy how quickly everyone is moving in this space. There are some still low-hanging fruit optimizations we're working on ( https://github.com/Mooncake-Labs/pg_mooncake/issues/82 ), and
44.
by moonikakiss 2y ago
well, pg_mooncake is a Postgres extension, and Postgres + pg_mooncake is still just Postgres. Users deploy pg_mooncake as a Postgres extension and write and query all tables through psql. Fast analytic databases need two key things: columna
45.
by moonikakiss 2y ago
Architecturally, it's very similar. We have the same vision! And they've done a great job, especially around writing to Iceberg. Some differences: 1. Our extension is fully open-source. I believe they've open-sourced bits of
46.
Postgres Just Cracked the Top Fastest Databases for Analytics(mooncake.dev)
378 points by moonikakiss 2y ago|120 comments
47.
Postgres is now top 10 fastest on Clickbench(github.com)
1 points by moonikakiss 2y ago|0 comments
48.
How to improve DuckDB performance on Parquet?(mooncake.dev)
1 points by moonikakiss 2y ago|0 comments
49.
Lotus: Semantic Query Engine(github.com)
1 points by moonikakiss 2y ago|0 comments