Jump toUpdate content

How to upgrade a Managed Database for PostgreSQL and MySQL

Published on 11 May 2019

You can upgrade your Database Instances in two ways: by increasing its Block Storage volume or by changing the node type.

Security & Identity (IAM):

You may need certain IAM permissions to carry out some actions described on this page. This means:

  • you are the Owner of the Scaleway Organization in which the actions will be carried out, or
  • you are an IAM user of the Organization, with a policy granting you the necessary permission sets
Requirements:

How to increase a Block Storage volume

Note:
  • Block Storage is available for Database Instances located in the PAR, AMS, and WAW regions.
  • Your Database requires you to have a Block Storage volume
  1. Scroll down to Volume settings in the overview page of your selected Database Instance.
  2. Click Increase Volume Size. A pop up appears.
  3. Specify your volume capacity (in GB). The amount you define will be your new volume capacity.
    Important:
    • You can increase your Block Storage volume to up to 10 TB.
    • Block volume sizes cannot be decreased.
  4. Click Increase Volume to confirm.

How to change the node type

In case you want to upgrade to an Instance with local storage, you have to change the Database node type.

  1. Click PostgreSQL and MySQL under Managed Databases on the side menu. A list of your Database Instances displays.
  2. Click the name of the Database Instance that you want to upgrade.
  3. Scroll down to the Node Settings section in the Database Information page. Then, click Modify Node Type.
  4. Choose the specifications of the new Database Instance from the dropdown list.
  5. Click Validate to confirm your choices.
    Important:

    Make sure that the Database Instance you choose provides sufficient disk space for your database. Otherwise, an error message will be displayed and the database will not be upgraded.

The action of changing the node type will perform a rolling upgrade of your Database Instance. During this process, the Database Instance will be unavailable for several tens of seconds.

See Also