News for hackers. Stuff that matters.

A comment on Postgres WASM. Parent comment

Re:Postgres WASM by chrisjc on Monday October 03, 2022 @12:06PM (#33069423)
> especially is storage is decoupled from compute!

This would be amazing! I can imagine a situation where external tables are managed by some MPP, and a WASM compute engine (Postgres, DuckDB, etc) would be able to at least read subsets/partitions of the full external table.

I wonder if the work required to make a native WASM Postgres would have to be split up into efforts for row-based vs column-based. Selfishly, I would love to have access to a column-based version first.

[ Parent | on HN ]
Re:Postgres WASM by pistoriusp on Monday October 03, 2022 @01:16PM (#33070570)
We actually kinda see parts of this in https://github.com/superfly/litefs, albeit for SQLite.

And here we see some ideas forming around "pluggable storage for PostgresQL": https://wiki.postgresql.org/wiki/Future_of_storage#Pluggable...

Seriously! If any of this sounds interesting to build, reach out, and we'll make it happen!

[ Parent | on HN ]