{"id":182581,"date":"2026-07-10T10:53:26","date_gmt":"2026-07-10T08:53:26","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/pgrust-klon-postgresql-na-rust-prohodyashhij-vse-regressionnye-testy"},"modified":"2026-07-10T10:53:26","modified_gmt":"2026-07-10T08:53:26","slug":"pgrust-klon-postgresql-na-rust-prohodyashhij-vse-regressionnye-testy","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/pgrust-klon-postgresql-na-rust-prohodyashhij-vse-regressionnye-testy","title":{"rendered":"pgrust \u2014 a clone of PostgreSQL in Rust, passing all regression tests","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The pgrust project has been published, featuring a PostgreSQL database management system rewritten in Rust using the c2rust translator and AI assistance. It is stated that the project is not yet ready for production use, but it successfully passes all PostgreSQL regression tests, is compatible with the data storage format of PostgreSQL 18.3, and can utilize data catalogs from PostgreSQL 18.3. The project code is distributed under the AGPLv3 license, unlike the original PostgreSQL, which is provided under the permissive PostgreSQL license, akin to BSD and MIT licenses. An online demonstration based on a WebAssembly build is available, as well as a Docker image for quick deployment. <\/p>\n
The development aims to achieve full compatibility with PostgreSQL 18.3, as well as to conduct experiments on altering the internal structure and creating a version of PostgreSQL free from architectural constraints that cannot be resolved due to historical reasons. The project successfully passes a set of over 46,000 PostgreSQL regression tests, but is currently incompatible with PostgreSQL extensions, does not provide the desired performance optimizations, and does not fully implement procedural languages PL\/Python, PL\/Perl, and PL\/Tcl. <\/p>\n
Future plans: <\/p>\n
\n
Translation to a multi-threaded internal architecture.\n
Implementation of connection pooling.\n
Optimization for workflows heavily utilizing JSON.\n
The ability to create copies and branches of database elements in Copy-on-Write mode without duplicating data.\n
Experiments with an architecture that does not require performing the VACUUM operation.\n
A SQL query constraint system that allows blocking excessive resource consumption during the execution of poor-quality queries.\n
Protection against the optimizer switching to less efficient query execution plans. <\/ul>\n
According to the project author, work is currently underway on the next version of pgrust, which replaces the worker pool with a multithreaded connection handling model. Additional optimizations are also being implemented, such as batch processing of rows in tables and preloading of data. When tested using percona-tpcc for transaction processing, the new version of pgrust proved to be 50% faster than the standard PostgreSQL, and 300 times faster for analytical queries. <\/p>\n
A hybrid approach was used when converting to Rust, where the PostgreSQL code was initially processed with the c2rust translator, generating an unsafe Rust representation that closely resembles the original C code structure. After processing in c2rust, approximately 1000 crate packages were created, which were simultaneously translated into idiomatic Rust using the AI model Claude and the Conductor toolkit to distribute tasks among concurrently running subagents. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"