PBXT is no longer maintained, and is not part of MariaDB 5.5 or later.
This page documents system variables related to the PrimeBase XT storage engine (PBXT). PBXT is no longer maintained, and is not part of MariaDB 5.5 or later.
See Server System Variables for a complete list of system variables and instructions on setting them.
See also the Full list of MariaDB options, system and status variables.
Variables that specify a number of bytes may include a unit indication after the value. For example: 100KB, 64MB, etc. There should be no space between the number and the unit. Units are case insensitive (KB = Kb = kb). If no unit is specified then bytes is assumed. The recognized units are:
Variables which use this type of value are: pbxt_index_cache_size
, pbxt_record_cache_size
, pbxt_log_cache_size
, pbxt_log_file_threshold
, pbxt_checkpoint_frequency
, pbxt_data_log_threshold
, pbxt_log_buffer_size
, pbxt_data_file_grow_size
, and pbxt_row_file_grow_size
.
PBXT stores part of the database in the data logs. This is mostly data from rows containing long VARCHAR fields or BLOB data. The data logs are managed by the "compactor" thread. When a record is deleted from a data log, the data is marked as garbage. When the total garbage in a data log reaches a certain threshold, the compactor thread compacts the data log by copying the valid data to a new data log, and deleting the old data log.
Option | Default Value |
---|---|
|
ON |
|
0 |
|
ON |
pbxt_auto_increment_mode
0
' (MySQL standard) or '1
' (Previous IDs are never re-used).--pbxt-auto-increment-mode=#
0
MariaDB 5.5
pbxt_checkpoint_frequency
--pbxt-checkpoint-frequency=#
24MB
MariaDB 5.5
pbxt_data_file_grow_size
--pbxt-data-file-grow-size=#
2MB
MariaDB 5.5
pbxt_data_log_threshold
--pbxt-data-log-threshold=#
64MB
MariaDB 5.5
pbxt_flush_log_at_trx_commit
0
' - Lowest durability, the transaction log is not written or flushed on transaction commit. In this case it is possible to loose transactions if the server executable crashes.1
' - Full-durability, the transaction log is written and flushed on every transaction commit.2
' - Medium durabilty, the transaction log is written, but not flushed on transaction commit. In this case it is possible to loose transactions of the server machine crashes (for example, a power failer).--pbxt-flush-log-at-trx-commit=#
1
MariaDB 5.5
pbxt_garbage_threshold
--pbxt-garbage-threshold=#
50
MariaDB 5.5
pbxt_index_cache_size
--pbxt-index-cache-size=#
32MB
MariaDB 5.5
pbxt_log_buffer_size
--pbxt-log-buffer-size=#
256MB
MariaDB 5.5
pbxt_log_cache_size
--pbxt-log-cache-size=#
32MB
MariaDB 5.5
pbxt_log_file_count
--pbxt-log-file-count=#
3
MariaDB 5.5
pbxt_log_file_threshold
--pbxt-log-file-threshold=#
32MB
MariaDB 5.5
pbxt_offline_log_function
0
' - Recycle log (default). This means the log is renamed and written again.1
' - Delete log (default on Mac OS X).2
' - Keep log. The logs can be used to repeat all operations that were applied to the database. --pbxt-offline-log-function=#
0
MariaDB 5.5
pbxt_record_cache_size
--pbxt-record-cache-size=#
32MB
MariaDB 5.5
pbxt_row_file_grow_size
--pbxt-row-file-grow-size=#
256KB
MariaDB 5.5
pbxt_sweeper_priority
0
' (Low), '1
' (Normal), or '2
' (High). The Sweeper is responsible for removing deleted records and index entries (deleted records also result from UPDATE statements). If many old deleted records accumulate search operations become slower. Therefore it may improve performance to increase the priority of the Sweeper on a machine with 4 or more cores. --pbxt-sweeper-priority=#
0
MariaDB 5.5
pbxt_support_xa
--pbxt-support-xa=#
TRUE
MariaDB 5.5
pbxt_transaction_buffer_size
--pbxt-transaction-buffer-size=#
1MB
MariaDB 5.5
© 2019 MariaDB
Licensed under the Creative Commons Attribution 3.0 Unported License and the GNU Free Documentation License.
https://mariadb.com/kb/en/pbxt-system-variables/