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
  • #4975
Closed
Open
Issue created Jan 09, 2020 by Ian Baum@ibaumMaintainer2 of 2 checklist items completed2/2 checklist items

PostgreSQL 11 upgrade procedure for GEO installations

We need to support upgrading GEO installations from PostgreSQL 9.6.x or 10.X to PostgreSQL 11.X. Initially this will be an opt-in upgrade, but will become opt out in %12.10 and mandatory prior to GitLab 13.0. PostgreSQL 9.6 and 10 are scheduled to be removed in GitLab 13.0.

The current procedure should not need to be deviated from significantly.

We should verify the following GEO installation types

  1. Single node primary and secondaries
  2. Separate database nodes on primary. Secondary with separate node running postgresql and geo-postgresql.

The pg-upgrade command does not currently support running on a secondary with separate nodes for postgresql and geo-postgresql. This is a major change that will be worked on separately in #4838 (closed)

Edited Apr 13, 2020 by Michael Kozono
Assignee
Assign to
Time tracking