expire_logs_days

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.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

See also: System Variables for MariaDB Enterprise Server 10.6, in 10.6 CS, in 10.5 ES, in 10.5 CS, in 10.4 ES, in 10.4 CS, in 10.3 ES, in 10.3 CS, in 10.2 ES, and in 10.2 CS

DETAILS

PARAMETERS

Command-line

--expire_logs_days=#

Configuration file

Supported

Dynamic

Yes

Scope

Global

Data Type

DOUBLE

Minimum Value

0

Maximum Value

99

Default Value

0.000000

CHANGE HISTORY

Release Series

History

10.6 Enterprise

  • Default value changed in MariaDB Enterprise Server 10.6.4-1 from 0 to 0.000000

10.6 Community

  • Present starting in MariaDB Community Server 10.6.0.

  • Default value changed in MariaDB Community Server 10.6.1 from 0 to 0.000000

10.5 Enterprise

  • Present starting in MariaDB Enterprise Server 10.5.3-1.

10.5 Community

  • Present starting in MariaDB Community Server 10.5.0.

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1.

10.4 Community

  • Present starting in MariaDB Community Server 10.4.0.

10.3 Enterprise

  • Present starting in MariaDB Enterprise Server 10.3.16-1.

10.3 Community

  • Present starting in MariaDB Community Server 10.3.0.

10.2 Enterprise

  • Present starting in MariaDB Enterprise Server 10.2.25-1.

10.2 Community

  • Present starting in MariaDB Community Server 10.2.0.

EXTERNAL REFERENCES