Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate Postgres to newer version #735

Closed
mrnicegyu11 opened this issue Sep 8, 2022 · 4 comments
Closed

Migrate Postgres to newer version #735

mrnicegyu11 opened this issue Sep 8, 2022 · 4 comments
Assignees
Labels
High Priority a totally crucial bug/feature to be fixed asap

Comments

@mrnicegyu11
Copy link
Member

We need to migrate our postgres database upwards, as our version is reaching end of lifetime

Message from aws:

Hello,
You are receiving this message because you have one or more Amazon RDS DB instances running with PostgreSQL major version 10 that requires your attention. Amazon RDS for PostgreSQL is announcing deprecation of its PostgreSQL major version 10, starting April 17, 2023. PostgreSQL community plans to deprecate PostgreSQL 10 on November 10, 2022 [1] and it will not receive any security patches after November 10, 2022. We strongly recommend that you monitor the PostgreSQL security page for documented vulnerabilities [2].
We recommend that you take action and upgrade your PostgreSQL databases running on major version 10 to a later major version, such as version 14. PostgreSQL 14 includes performance improvements for parallel queries, heavily-concurrent workloads, partitioned tables, logical replication, and vacuuming. To learn more about the benefits of PostgreSQL 14, please refer to ‘PostgreSQL 14 Community Release Announcement’ [3]
To upgrade your DB instance from major version 10, we recommend that you first upgrade your current version of database to a minor version such as 10.19 or later that has an upgrade path to the target major version, and then perform an upgrade to a later major version, such as 14. You can initiate an upgrade by going to the Modify DB Instance page in the AWS Management Console and change the database version setting to a newer major version of PostgreSQL. Alternatively, you can also use the AWS CLI to perform the upgrade. While major version upgrades typically complete within the standard maintenance window, the duration of the upgrade depends on the number of objects within the database. To avoid any unplanned unavailability outside your maintenance window, we recommend that you first take a snapshot of your database and test the upgrade to get an estimate of the upgrade duration. To learn more about upgrading PostgreSQL major versions in RDS, review the 'Upgrading Database Versions' page [4].
The upgrade process will shutdown the database instance, perform the upgrade, and restart the database instance. The DB instance may restart multiple times during the process. If you choose the "Apply Immediately" option, the upgrade will be initiated immediately after clicking on the "Modify DB Instance" button. If you choose not to apply the change immediately, the upgrade will be performed during your next maintenance window.
Your affected Amazon RDS DB Instances are listed in "Affected Resources" tab of the AWS Health Dashboard.
@mrnicegyu11 mrnicegyu11 added the High Priority a totally crucial bug/feature to be fixed asap label Sep 8, 2022
@sanderegg
Copy link
Member

sanderegg commented Sep 9, 2022

possible workflow for testing:

final migration shall be devised later on

@sanderegg sanderegg transferred this issue from ITISFoundation/osparc-issues Oct 5, 2022
@sanderegg sanderegg transferred this issue from ITISFoundation/osparc-simcore Oct 5, 2022
@sanderegg
Copy link
Member

@mrnicegyu11 this can be closed after the release 1.39.0 right?

@mrnicegyu11
Copy link
Member Author

@sanderegg , yes, this should be done and the issue can be closed as of today :)

@mrnicegyu11
Copy link
Member Author

this is done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High Priority a totally crucial bug/feature to be fixed asap
Projects
None yet
Development

No branches or pull requests

3 participants