Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • omnibus-gitlab omnibus-gitlab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1,061
    • Issues 1,061
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 67
    • Merge requests 67
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • omnibus-gitlabomnibus-gitlab
  • Issues
  • #5423
Closed
Open
Issue created Jun 05, 2020 by Hossein Pursultani@pursultaniDeveloper2 of 3 checklist items completed2/3 checklist items

Ensure Patroni detects PosgtreSQL upgrade

The initial implementation of Patroni in !3984 (merged) is only tested against PostgreSQL 11. When PostgreSQL 12 is shipped, the upgraded procedure with gitlab-ctl pg-upgrade must be verified with Patroni. Currently it fails.

We must ensure that:

  • pg-upgrade works on Patroni nodes
  • The procedure for upgrading a cluster is documented
  • Patroni can detect the upgrade and the difference between the running version and the upgraded version (postgresql::enable recipe already does this and warns the user if there is a difference) (the upgrade procedure restarts the service and this is not relevant anymore).
Edited Sep 08, 2020 by Hossein Pursultani
Assignee
Assign to
Time tracking