plrust.io

What It Is

PL/Rust is a loadable procedural language extension for PostgreSQL that allows developers to write database functions in Rust and compile them to native machine code for execution. Unlike interpreted procedural languages, it emphasizes performance, Rust’s compile-time safety guarantees, and access to the Rust ecosystem. The project is open source and actively developed on GitHub.

Core Capabilities

Functionally, PL/Rust covers the key scenarios for developing functions inside PostgreSQL: regular functions, arguments and return types, set-returning functions, triggers, SPI, dynamic function calls, and more. It provides access to the PostgreSQL Server Programming Interface, including dynamic queries, prepared statements, and cursors. It also offers safe Rust type wrappers for common types such as TEXT, INT, BIGINT, NUMERIC, FLOAT, DOUBLE PRECISION, DATE, and TIME. Technically, PL/Rust is built on pgrx, and each LANGUAGE plrust function can be viewed as a small pgrx extension.

Security and Deployment

A major selling point of PL/Rust is Rust’s type safety and memory safety. It uses the Rust compiler to prevent user functions from using unsafe, and relies on plrust-trusted-pgrx to restrict the available pgrx capabilities. On Linux x86_64 and aarch64, when compiled with the trusted feature and used with postgrestd, it can restrict access to the filesystem and host operating system. However, the documentation also makes clear that this is not a sandbox and should not be treated as a strong security boundary. Other platforms can use untrusted mode, but with weaker security guarantees. Installation involves PostgreSQL extensions, Rust compilation targets, postgrestd, and potentially cross-compilation configuration, so the setup is fairly complex.

Pricing and Documentation

The main text does not mention commercial pricing or paid editions, so it can only be assessed as an open-source project. The documentation covers installation, Docker trials, function usage, data types, SPI, architecture, external dependencies, linting, environment variables, and more, with a fairly systematic structure. However, the site also notes that the documentation is still under development, and some sections, such as the cross-compilation guide, remain incomplete.

Pros, Cons, and Ideal Users

Its strengths are strong performance potential, robust type safety, the ability to leverage the Rust ecosystem, and deep PostgreSQL integration. Its drawbacks are the relatively high installation and operations barrier, limited platform support for trusted mode, and the fact that third-party crate dependencies may still use unsafe. It is well suited to teams familiar with Rust and PostgreSQL internals that need to run high-performance logic on the database side. For ordinary SQL business logic or users looking for low-friction scripting extensions, PL/pgSQL, PL/Python, or existing C/pgrx extension approaches may be a better fit.

Access from China

The crawled text does not provide information about access from mainland China, mirrors, payment, or network availability, so its China access status is unknown. If it depends on GitHub, crates.io, or docs.rs, practical use may need to be evaluated against the local network environment.