This looks impressive. Could someone familiar with Postgres internals explain the hidden trade-offs of this approach?
I understand the obvious limitations of it being embedded/single-host, but I'm curious about the engine itself. Does running in this environment compromise standard features like ACID compliance, parallel query execution, or the ecosystem of tools/extensions we usually rely on?
You might want to have a look at our extensions catalog page: https://pglite.dev/extensions/
The key limitation (at the moment) is that it only supports a single connection. W're planning to lift that limitation though.