is presented beta version of the storage engine Orioledb Beta7 and the results of new tests are published that show a significant increase in performance compared to the traditional postgreSQL. In the Beta7 version, optimization was introduced aimed at improving work with multi -flow loads and accelerating reading and recording operations. The first stable release of Orioledb is planned to be formed in 2025. The engine is written in the language of si and is distributed under the postgresql license, similar to the BSD and mit.
license.
The ORIOLEDB project is developing an alternative storage engine for postgreSQL, designed to overcome the restrictions of the standard storage mechanism and increase the overall efficiency of the system. For example,
ORIOLEDB allows you to do without periodic performing the operation vacuum for the assembly of garbage, thanks Concurrency Control) based on Logs logs operating at the level of individual blocks and lines, as well as a system of automatic fusion of pages containing data. ORIOLEDB also uses 64-bit transaction identifiers, which solves the problem with the overflow of meters.
To simplify the use in distributed systems and parallelization of operations in Orioledb, the conduct is organized
Wal-log transaction levels at the level of rows. When performing the Update operation, it is supported to replace the data at the place (without the release of the current recording and creating a new one), which positively affects performance. ORIOLEDB also implements such opportunities as reading pages with data without using locks, direct connecting pages in RAM with pages in constant storage, using the COW mechanism (Copy-on-Write) when fixing control points to create non-proceeding snapshots at any time , storing data storage in compressed form using the ZSTD algorithm.
Of the Orioledb restrictions present in the seventh beta version, the possibility of using only indexes in B-Tree format (in the future will support all types of postgersql indices), as well as the lack of support for pre-prepared transactions (prepare transaction ) and commands Reindex ” in “Concurrently” mode. Orioledb is implemented in the form of a connected expansion requiring the introduction changes in the main code of postgresql.
In performance tests tpc–C