All pages
Powered by GitBook
1 of 1

Loading...

Upgrading from MariaDB 10.6 to MariaDB 10.7

An upgrading guide for unmaintained versions of MariaDB Community Server.

Note that is only maintained for one year. MariaDB 10.6 is currently the latest long-term maintenance release.

How to Upgrade

For Windows, see Upgrading MariaDB on Windows.

For MariaDB Galera Cluster, see Upgrading from MariaDB 10.6 to MariaDB 10.7 with Galera Cluster instead.

Before you upgrade, it would be best to take a backup of your database. This is always a good idea to do before an upgrade. We would recommend mariadb-backup.

The suggested upgrade procedure is:

  1. Modify the repository configuration, so the system's package manager installs . For example,

  • On Debian, Ubuntu, and other similar Linux distributions, see for more information.

  • On RHEL, CentOS, Fedora, and other similar Linux distributions, see for more information.

  • On SLES, OpenSUSE, and other similar Linux distributions, see for more information.

  1. .

  2. Uninstall the old version of MariaDB.

  • On Debian, Ubuntu, and other similar Linux distributions, execute the following:sudo apt-get remove mariadb-server

  • On RHEL, CentOS, Fedora, and other similar Linux distributions, execute the following:sudo yum remove MariaDB-server

  • On SLES, OpenSUSE, and other similar Linux distributions, execute the following:sudo zypper remove MariaDB-server

  1. Install the new version of MariaDB.

  • On Debian, Ubuntu, and other similar Linux distributions, see for more information.

  • On RHEL, CentOS, Fedora, and other similar Linux distributions, see for more information.

  • On SLES, OpenSUSE, and other similar Linux distributions, see for more information.

  1. Make any desired changes to configuration options in , such as my.cnf. This includes removing any options that are no longer supported.

  2. .

  3. Run .

  • mariadb-upgrade does two things:

    1. Ensures that the system tables in the database are fully compatible with the new version.

    2. Does a very quick check of all tables and marks them as compatible with the new version of MariaDB .

Incompatible Changes Between 10.6 and 10.7

On most servers upgrading from 10.6 should be painless. However, there are some things that have changed which could affect an upgrade:

Reserved Words

  • ROW_NUMBER is now a .

Compression

If a non-zlib compression algorithm was used in or before upgrading to 10.7, those tables will be unreadable until the appropriate compression library is installed. See .

Options That Have Changed Default Values

Option
Old default
New default

Options That Have Been Removed or Renamed

The following options should be removed or renamed if you use them in your :

Option
Reason

See Also

This page is licensed: CC BY-SA / Gnu FDL

-1

1

-1

1

-1

16000

-1

16000

-1

0

-1

16000

-1

0

-1

6

-1

2

-1

51

-1

1

-1

0

-1

2

-1

2

-1

1

-1

0

-1

9223372036854775807

-1

0

-1

0

-1

0

-1

1024

-1

9223372036854775807

-1

0

-1

0

-1

0

-1

1

-1

1

-1

1

-1

32767

-1

100

-1

600

-1

600

-1

3

-1

10485760

-1

1024

-1

0

-1

1

-1

0

-1

1

-1

2

-1

1

-1

1

-1

1

Upgrading from MariaDB 10.3 to MariaDB 10.4

spider_auto_increment_mode

-1

0

spider_bgs_first_read

-1

2

spider_bgs_mode

-1

0

spider_bgs_second_read

-1

Use instead.

Use instead.

Updating the MariaDB APT repository to a New Major Release
Updating the MariaDB YUM repository to a New Major Release
Updating the MariaDB ZYpp repository to a New Major Release
Stop MariaDB
Installing MariaDB Packages with APT
Installing MariaDB Packages with YUM
Installing MariaDB Packages with ZYpp
option files
Start MariaDB
mariadb-upgrade
mysql
reserved word
InnoDB
Mroonga
Compression Plugins#Upgrading
option files
Upgrading from MariaDB 10.5 to MariaDB 10.6
Upgrading from MariaDB 10.4 to MariaDB 10.5

100

spider_bka_mode
spider_bka_table_name_type
spider_buffer_size
spider_bulk_size
spider_bulk_update_mode
spider_bulk_update_size
spider_casual_read
spider_connect_timeout
spider_crd_bg_mode
spider_crd_interval
spider_crd_mode
spider_crd_sync
spider_crd_type
spider_crd_weight
spider_delete_all_rows_type
spider_direct_dup_insert
spider_direct_order_limit
spider_error_read_mode
spider_error_write_mode
spider_first_read
spider_init_sql_alloc_size
spider_internal_limit
spider_internal_offset
spider_internal_optimize
spider_internal_optimize_local
spider_load_crd_at_startup
spider_load_sts_at_startup
spider_low_mem_read
spider_max_order
spider_multi_split_read
spider_net_read_timeout
spider_net_write_timeout
spider_quick_mode
spider_quick_page_byte
spider_quick_page_size
spider_read_only_mode
spider_reset_sql_alloc
spider_second_read
spider_selupd_lock_mode
spider_semi_split_read
spider_semi_split_read_limit
spider_semi_table_lock_connection
spider_reset_sql_alloc
Upgrading from MariaDB 10.6 to MariaDB 10.11 with Galera Cluster
wsrep_replicate_myisam
wsrep_mode
wsrep_strict_ddl
wsrep_mode
MariaDB 10.7
MariaDB 10.7
The features in MariaDB 10.7