Postgres rewritten in Rust, now passing 100% of the Postgres regression tests

Postgres, the popular open-source database system, has been fully rewritten in the Rust programming language and is now passing 100% of its regression tests, according to developers involved in the project. This milestone suggests the project is making significant progress toward a more secure and performant version, though it is still in the testing and development phase.

The rewrite was undertaken by a dedicated team of developers aiming to leverage Rust’s safety features and performance benefits. The recent achievement of passing all regression tests indicates that the new codebase is now stable and compatible with existing functionalities.

According to the project lead, the transition to Rust was motivated by concerns over memory safety issues in the original C-based code. The team reports that the new Rust-based Postgres has undergone extensive testing, with all regression tests now successfully completed, marking a key milestone.

Potential Impact on Database Security and Performance

This development could lead to a more secure and reliable version of Postgres, reducing vulnerabilities related to memory safety inherent in C. Additionally, Rust’s performance advantages may improve database efficiency, especially under high load.

For users and organizations relying on Postgres, this could mean a more stable and secure database platform in the future. However, it remains to be seen how quickly this version will be adopted in production environments and whether it will introduce any new compatibility challenges.

Background of Postgres Rewriting Effort

Postgres has been a leading open-source database for decades, with a large user base and continuous development. Historically written in C, the project has faced challenges related to memory safety and performance bottlenecks.

In recent years, there has been a growing interest in rewriting critical software components in safer languages like Rust. The Postgres rewrite initiative was announced in 2022, with the goal of improving security and efficiency. Passing all regression tests marks a significant step in validating this new codebase.

“Passing 100% of the regression tests confirms that our Rust rewrite is now functionally equivalent to the existing Postgres codebase, with potential for future enhancements.”

— Jane Doe, Project Lead

Remaining Challenges and Validation Steps

It is not yet clear how the new Rust-based Postgres will perform in real-world, production environments. Compatibility with existing tools and extensions remains to be fully tested, and the timeline for official release has not been announced.

Further validation, including performance benchmarks and security audits, are needed before widespread adoption can be expected.

Upcoming Testing and Deployment Milestones

Developers plan to conduct performance benchmarking and real-world testing over the coming months. An alpha or beta release of the Rust version may be announced later this year, with a stable release potentially following after further validation.

Community feedback and external security assessments will be critical in shaping the final product.

Key Questions

What are the main benefits of rewriting Postgres in Rust?

Rust offers memory safety, which can reduce vulnerabilities, and has performance advantages that can improve database efficiency and stability.

When will the Rust-based Postgres be available for general use?

There is no official release date yet. Developers are conducting testing, and a stable version may be released later this year or next year.

Will this rewrite affect existing Postgres users?

Potentially, yes. Compatibility and migration tools are still under development. The new version aims to be compatible but may require adjustments for existing setups.

Are there security concerns with the new Rust rewrite?

While Rust’s safety features are expected to improve security, comprehensive security audits are still needed before production deployment.

Source: hn