pglite-oxide: embedded Postgres for Rust and Tauri apps

For years, the 'local Postgres' problem in Rust has been a choice between the overhead of Docker/Testcontainers or the architectural mismatch of SQLite. pglite-oxide attempts to bridge this gap by embedding the Electric SQL PGlite runtime using a WASI (WebAssembly System Interface) approach. By leveraging Wasmtime, it allows developers to ship a full Postgres-compatible environment inside their binary, which is a significant win for Tauri desktop apps and CI pipelines where spinning up a heavy container is a bottleneck. Technically, the project is a smart piece of glue. Instead of fighting with fragile native bindings to libpglite, it treats the Postgres runtime as a Wasm module. The use of a bundled PGDATA template and a compiled module cache shows an understanding of the cold-start problem inherent in Wasm. The dual-interface design is particularly practical: the `Pglite` API is for those who want tight integration, while `PgliteServer` provides a standard connection URI, allowing existing crates like SQLx to work without modification. However, there are inherent trade-offs. Because it's a Wasm-based embedding, you aren't getting raw native C performance, and the documentation notes that the runtime owns a single backend—meaning connection pooling must be configured carefully to avoid contention. It is not a replacement for a production-grade Postgres server, but as a development and testing tool, it is remarkably lean. This is a high-utility tool for Rust engineers who are tired of managing database dependencies in their local environment or for Tauri developers who need a robust relational store that doesn't require the user to install a database engine. It turns Postgres from a piece of infrastructure into a library dependency.