Skip to main content

PostgreSQL: No More VACUUM, No More Bloat

· 5 min read
Alexander Korotkov
Creator of OrioleDB

PostgreSQL, a powerful open-source object-relational database system, has been lauded for its robustness, functionality, and flexibility. However, it is not without its challenges – one of which is the notorious VACUUM process. However, the dawn of a new era is upon us with OrioleDB, a novel engine designed for PostgreSQL that promises to eliminate the need for the resource-consuming VACUUM.

OrioleDB is now in Beta

· One min read
Alexander Korotkov
Creator of OrioleDB
Pavel Borisov
PostgreSQL contributor

Long story short, OrioleDB alpha version was released more than year ago. More than 200 bugs were fixed since then. Now, OrioleDB reached beta stage. That means we recommend OrioleDB for pre-production testing. The most interesting workloads for testing could include: high transaction throughput, high volume of updates, high volume of in-memory operations, lock bottlenecks and other extreme cases.

Rethinking PostgreSQL buffer mapping for modern hardware architectures

· 6 min read
Alexander Korotkov
Creator of OrioleDB

Traditional database engines were designed in the '80s and early '90s. At that time CPUs were much slower than they are today. Even worse was storage, hard drive head positioning time was enormous1. And CPU (or, at most, a few single-core CPUs) was assumed to be infinitely fast in comparison to IOPS. Therefore, systems were designed to save IOPS as much as possible, while CPU overhead was considered a secondary optimization target.


  1. Numbers Every Programmer Should Know By Year - Colin Scott