MatrixDB 4 small version upgrade

Small version upgrade refers to upgrading to a new version under the premise that the main version number remains unchanged. For example: upgrade from 4.0.0 to 4.0.2; upgrade from 4.0.0 to 4.1.0

Below, take the example of upgrading from MatrixDB 4.0.0 to 4.3.0, and introduce the detailed steps:

1. Get the latest installation package

Obtain the 4.3.0 installation package, matrixdb-4.3.0-1.el7.x86_64.rpm from the official website, and copy it to all nodes.

2. Stop the cluster

Switch to mxadmin to execute gpstop -af:

su - mxadmin
gpstop -af

3. Execute update commands on all nodes

Use root account to upgrade rpm package:

yum upgrade matrixdb-4.3.0-1.el7.x86_64.rpm

Note, do not use yum erase, otherwise the configuration of the previous version will be deleted.

4. Restart mxui

systemctl restart matrixdb.supervisor.service

5. Modify the configuration and restart the cluster (4.3.10 and later versions can be skipped)

Log in to the master host, switch to the mxadmin account, start the cluster first, add the mars plugin to the shared_preload_libraries configuration and restart:

su - mxadmin
gpstart -a
gpconfig -c shared_preload_libraries -v "matrixts,matrixmgr,matrixgate,telemetry,mars"
gpstop -arf

Note: The value of shared_preload_libraries needs to be added to the original configuration

6. Upgrade plug-in

If you use the matrixts plugin and mars plugin, connect to the database and upgrade using the following SQL commands:

ALTER EXTENSION matrixts UPDATE;
ALTER EXTENSION mars UPDATE;