pgrust: A Rust rewrite of Postgres.
What problem it solves
The project reimagines Postgres as a modern database implementation while retaining wire and SQL dialect compatibility with Postgres. It also addresses database resilience by reworking concurrency, query scheduling, memory management, and core storage components.
Key features
Gravity query engine — Gravity provides a vectorized, push-based query engine with a JIT that compiles plans to AArch64 or x86-64 machine code, WebAssembly in the browser build, or an interpreter when compilation is not worthwhile.
Source: README
Columnar storage — The pgrcolumnar table access method stores compressed, immutable parts with zone maps, delete vectors, and background compaction. It supports transactional writes, MVCC snapshots, WAL logging, replication, row locks, and several index types.
Source: README
Thread-based concurrency — Connections and parallel queries use threads rather than processes. Parallel work is organized around work stealing, allowing idle threads to assist queries already in flight.
Source: README
Priority-aware query scheduler — Queries receive priorities, and the priority of long-running queries is lowered so heavy workloads interfere less with fast queries.
Source: README
Automatic memory management — A unified memory budget covers the buffer pool, columnar caches, and running queries. Near the limit, the server can cancel the statement using the most memory instead of allowing the operating system to terminate it.
Source: README
Quick start
Copied verbatim from the project's README.
docker run -d --name pgrust -e POSTGRES_PASSWORD=secret -p 5432:5432 malisper/pgrust:v0.4-betapsql -h localhost -p 5432 -U postgres
docker exec -it pgrust psql -U postgresWho it may suit
Inference: may suit developers experimenting with Rust database engines, Postgres-compatible tooling, columnar storage, or browser-hosted database demonstrations. The README does not recommend production use yet and identifies testing and reliability as the current priority.
Topics to discuss
Which Postgres behaviors are most important to verify before moving beyond beta?
How should differential fuzzing, simulation testing, and formal verification be prioritized?
What workloads and deployment scenarios would be most useful for community testing of the columnar storage and query scheduler?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/malisper/pgrust#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…