expire_logs_days

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.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, and in 10.4 ES

DETAILS

PARAMETERS

Dynamic

Yes

Scope

Global

Data Type

DOUBLE

Minimum Value

0

Maximum Value

99

Default Value

0.000000

SKYSQL

Cloud

SkySQL Topology

ES Ver

Default

AWS

HA (Primary/Replica)

10.4

4

AWS

HA (Primary/Replica)

10.5

4

AWS

Transactional Standalone

10.4

4

AWS

Transactional Standalone

10.5

4

AWS

Distributed Transactions

10.5

0

GCP

ColumnStore

10.5

0

GCP

ColumnStore Multi

10.5

0

GCP

Galera

10.4

4

GCP

Galera

10.5

4

GCP

HA (Primary/Replica)

10.4

4

GCP

HA (Primary/Replica)

10.5

4

GCP

HTAP

10.5

0

GCP

Transactional Standalone

10.4

4

GCP

Transactional Standalone

10.5

4

GCP

Distributed Transactions

10.5

0

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

  • Present starting in MariaDB Enterprise Server 10.5.3-1.

10.4 Enterprise

  • Present starting in MariaDB Enterprise Server 10.4.6-1.

EXTERNAL REFERENCES