The PBXT storage engine is included in the MariaDB source and binaries by default.
In MariaDB 5.5, the PBXT storage engine is disabled by default and must be explicitly built to use it. The reason is that PBXT is not actively maintained anymore, it has a few bugs that are not fixed and it's not actively used.
PBXT versions in various releases are:
PBXT is a general purpose transactional storage engine. PBXT is fully "ACID" compliant, which means it can be used as an alternative to other MariaDB transactional engines (such as XtraDB or InnoDB).
PBXT features include the following:
- MVCC Support: MVCC stands for Multi-version Concurrency Control. MVCC allows reading the database without locking.
- Fully ACID compliant: This means that all transactions are: atomic, consistent, isolated and durable.
- Row-level locking: When updating, PBXT uses row-level locking. Row-level locking is also used during SELECT FOR UPDATE.
- Fast Rollback and Recovery: PBXT uses a specialized method to identify garbage which makes "undo" unnecessary. This make both rollback of transactions and recovery after restart very fast.
- Deadlock Detection: PBXT identifies all kinds of deadlocks immediately.
- Write-once: PBXT uses a log-based storage which makes it possible to write transactional data directly to the database, without first being writen to the transaction log.
- Referential Integrity: PBXT supports foreign key definitions, including cascaded updates and deletes.
- BLOB streaming: In combination with the BLOB Streaming engine PBXT can stream binary and media directly in and out of the database.
PBXT will not take any resources (disk space or CPU processing) until you create your first PBXT table.
xtstat program can be used to monitor all internal activity of PBXT. See xtstat for more information.
Further documentation for PBXT can be found here: http://www.primebase.org/documentation