Skip to content

Fix incorrect PG upgrading on upgrading to GitLab 13.0

Takuya Noguchi requested to merge 8170-pg-upgrade-on-gitlab-13.0-releasenote into master

Why is this change being made?

The original release post (!48201 (merged)) described in the incorrect way for the behavior of 13.0.x omnibus package. That was double-checked by @twk3 (see gitlab-org/omnibus-gitlab#5412 (comment 373469831)).

cf. gitlab-org/omnibus-gitlab!4186 (merged) and https://docs.gitlab.com/omnibus/settings/database.html#gitlab-1210-and-later

Author Checklist

  • Correct MR template applied (e.g blog post)
  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

Closes #8170 (closed)

Edited by Takuya Noguchi

Merge request reports