4 ms·
> 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 c
by chrisjc 4y ago
> 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.
- pistoriusp 4y agoWe actually kinda see parts of this in https://github.com/superfly/litefs 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_storage_for_tables 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!