expire_logs_days
This page is part of MariaDB's Documentation.
The parent of this page is: System Variables for MariaDB Enterprise Server
Topics on this page:
Overview
In 10.6 ES, 10.6 CS:
If non-zero, binary logs will be purged after expire_
logs_ days days; It and binlog_ expire_ logs_ seconds are linked, such that changes in one are converted into the other, presentable as a decimal value with 1/1000000 of the day precision; possible purges happen at startup and at binary log rotation
In 10.6 ES:
If non-zero, binary logs will be purged after expire_
logs_ days days; It and binlog_ expire_ logs_ seconds are linked, such that changes in one are converted into the other, presentable as a decimal value with 1/1000000 of the day precision; possible purges happen at startup and at binary log rotation
In 10.5 ES, 10.5 CS, 10.4 ES, 10.4 CS, 10.3 ES, 10.3 CS, 10.2 ES, 10.2 CS:
If non-zero, binary logs will be purged after expire_
logs_ days days; possible purges happen at startup and at binary log rotation
In 10.5 ES, 10.4 ES:
If non-zero, binary logs will be purged after expire_
logs_ days days; possible purges happen at startup and at binary log rotation
See also: System Variables for MariaDB Enterprise Server 10.6, in 10.5 ES, in 10.4 ES, in 10.3 ES, in 10.2 ES, in 10.6 CS, in 10.5 CS, in 10.4 CS, in 10.3 CS, and in 10.2 CS
See also: System Variables for MariaDB Enterprise Server 10.6, in 10.5 ES, and in 10.4 ES
USAGE
DETAILS
SYNONYMS
SCHEMA
PARAMETERS
Command-line | --expire_logs_days=# |
Configuration file | Supported |
Dynamic | Yes |
Scope | Global |
Data Type | DOUBLE |
Minimum Value | 0 |
Maximum Value | 99 |
Product Default Value | 0.000000 |
SKYSQL
Cloud | SkySQL Topology | ES Ver | Service Default |
---|---|---|---|
AWS | Multi-Node Analytics | 10.6 | 0.000000 |
Single Node Analytics | 10.6 | 0.000000 | |
Replicated Transactions | 10.4 | 4 | |
10.5 | 4 | ||
10.6 | 4.000000 | ||
Single Node Transactions | 10.4 | 4 | |
10.5 | 4 | ||
10.6 | 4.000000 | ||
GCP | Multi-Node Analytics | 10.6 | 0.000000 |
Single Node Analytics | 10.6 | 0.000000 | |
Replicated Transactions | 10.4 | 4 | |
10.5 | 4 | ||
10.6 | 4.000000 | ||
Single Node Transactions | 10.4 | 4 | |
10.5 | 4 | ||
10.6 | 4.000000 |
Cloud | SkySQL Topology | ES Ver | Service Default |
---|---|---|---|
AWS | ColumnStore Data Warehouse | 10.6 | 0.000000 (minimum value: 0, maximum value: 99) |
Enterprise Server With Replica(s) | 10.4 | 4 (minimum value: 0, maximum value: 99) | |
10.5 | 4 (minimum value: 0, maximum value: 99) | ||
10.6 | 4.000000 (minimum value: 0, maximum value: 99) | ||
Enterprise Server Single Node | 10.4 | 4 (minimum value: 0, maximum value: 99) | |
10.5 | 4 (minimum value: 0, maximum value: 99) | ||
10.6 | 4.000000 (minimum value: 0, maximum value: 99) | ||
GCP | ColumnStore Data Warehouse | 10.6 | 0.000000 (minimum value: 0, maximum value: 99) |
Enterprise Server With Replica(s) | 10.4 | 4 (minimum value: 0, maximum value: 99) | |
10.5 | 4 (minimum value: 0, maximum value: 99) | ||
10.6 | 4.000000 (minimum value: 0, maximum value: 99) | ||
Enterprise Server Single Node | 10.4 | 4 (minimum value: 0, maximum value: 99) | |
10.5 | 4 (minimum value: 0, maximum value: 99) | ||
10.6 | 4.000000 (minimum value: 0, maximum value: 99) |
See SkySQL details in MariaDB SkySQL previous release
See SkySQL details in MariaDB SkySQL new release
PRIVILEGES
EXAMPLES
ERROR HANDLING
FEATURE INTERACTION
RESPONSES
DIAGNOSIS
ISO 9075:2016
CHANGE HISTORY
Release Series | History |
---|---|
10.6 Enterprise |
|
10.6 Community |
|
10.5 Enterprise |
|
10.5 Community |
|
10.4 Enterprise |
|
10.4 Community |
|
10.3 Enterprise |
|
10.3 Community |
|
10.2 Enterprise |
|
10.2 Community |
|
Release Series | History |
---|---|
10.6 Enterprise |
|
10.5 Enterprise |
|
10.4 Enterprise |
|
RELATED TOPICS
EXTERNAL REFERENCES
Additional information on this topic may be found in the MariaDB Public Knowledge Base.