-
Notifications
You must be signed in to change notification settings - Fork 28
♻️ ⬆️ ⚗️ ⚠️ upgrade to postgres 17.2 (DONT MERGE) #7023
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
base: master
Are you sure you want to change the base?
♻️ ⬆️ ⚗️ ⚠️ upgrade to postgres 17.2 (DONT MERGE) #7023
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #7023 +/- ##
==========================================
+ Coverage 87.70% 87.87% +0.17%
==========================================
Files 1635 1713 +78
Lines 63943 65962 +2019
Branches 1178 1166 -12
==========================================
+ Hits 56079 57962 +1883
- Misses 7552 7666 +114
- Partials 312 334 +22
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
CC @sanderegg @YuryHrytsuk @matusdrobuliak66 didnt check the failing tests yet (I guess it's only codecov so this should be fine), anyone willing to help next sprint: would be very appreciated :--) |
This needs to be manually rolled-out, re-importing the DB from a dump, with maintenance downtime, and requires changes in aws/terraform for the RDS. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please add a # devops
section with the required actions from devops at the top of the ticket
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what kind of help do you need? it looks all green.
I guess the only thing needed is the data migration (pg_upgrade or dump/reload)
True thanks, I wrote the text assuming there would be issues, before the result of the tests was there. All good I think :--) |
@matusdrobuliak66 you mentioned once that we could do some sort of pruning /reindexing of the db. Perhaps we can take advantage ot hits to do so? |
We can do this (mainly the second step):
|
|
…TISFoundation#7320) Co-authored-by: Giancarlo Romeo <giancarloromeo@gmail.com> Co-authored-by: Sylvain <35365065+sanderegg@users.noreply.github.com>
…DB disable write to disk (ITISFoundation#7403)
Co-authored-by: Pedro Crespo-Valero <32402063+pcrespov@users.noreply.github.com>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Co-authored-by: Odei Maiz <33152403+odeimaiz@users.noreply.github.com>
|
What do these changes do?
Related issue/s
ITISFoundation/osparc-ops-environments#907
Dev-ops checklist