[PG16][Phase 1] Risk assessment and configuration review for releases v15 and v16
Summary
This is not a blocker issue
Instead of a full and formal risk assessment, we'll try to improve our logical replication, to allow a test in production for a certain amount of time and also allow a quick rollback in order to revert if issues are found in production.
On this issue we assess documentation to figure any potential configuration deprecation, new settings benefits and risks for the upgrade of our databases from version 14 to 16, looking for new features or existing bugs that might risk negative performance impact.
We are not going to benchmark v14 vs v16 with synthetic benchmarking in Gitlabs environment.
DRIs
- DBRE contact for this request: @rhenchen.gitlab
- SRE contact for this request:
- QA contact for this request:
- Backend Engineer contact for this request:
- Manager contact for this request:
Tasks
-
Review the release notes -
Review community benchmarking between v14 vs v15
andv15 vs v16
-
Review existing critical bugs on v15 and v16
Desired Outcome/Acceptance Criteria
-
List any deprecated config settings; -
List new settings that could be beneficial; -
List features that might regress performance or availability; -
List critical unresolved bugs;
Edited by Rafael Henchen