Skip to content
代码片段 群组 项目
未验证 提交 dd39e737 编辑于 作者: Evan Read's avatar Evan Read 提交者: GitLab
浏览文件

Merge branch 'cb-pg-16-default-docs' into 'master'

Announce PostgreSQL 14 and 15 deprecation

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/182866



Merged-by: default avatarEvan Read <eread@gitlab.com>
Approved-by: default avatarMartin Brümmer <mbruemmer@gitlab.com>
Approved-by: default avatarDenis Afonso <dafonso@gitlab.com>
Approved-by: default avatarEvan Read <eread@gitlab.com>
Reviewed-by: default avatarClemens Beck <cbeck@gitlab.com>
Co-authored-by: default avatarClemens Beck <cbeck@gitlab.com>
Co-authored-by: default avatarPeter Lu <plu@gitlab.com>
No related branches found
No related tags found
2 合并请求!3031Merge per-main-jh to main-jh by luzhiyuan,!3030Merge per-main-jh to main-jh
- title: "PostgreSQL 14 and 15 no longer supported"
removal_milestone: "18.0"
announcement_milestone: "17.9"
breaking_change: true
reporter: clemensbeck
impact: medium
scope: instance
resolution_role: Admin
manual_task: true
stage: systems
issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/521663
body: |
GitLab follows an [annual upgrade cadence for PostgreSQL](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/data-access/database-framework/postgresql-upgrade-cadence/).
Support for PostgreSQL 14 and 15 is scheduled for removal in GitLab 18.0.
In GitLab 18.0, PostgreSQL 16 becomes the minimum required PostgreSQL version.
PostgreSQL 14 and 15 will be supported for the full GitLab 17 release cycle.
PostgreSQL 16 will also be supported for instances that want to upgrade prior to GitLab 18.0.
If you are running a single PostgreSQL instance you installed by using an Omnibus Linux package, an automatic upgrade may be attempted with 17.11.
Make sure you have enough disk space to accommodate the upgrade. For more information, see the [Omnibus database documentation](https://docs.gitlab.com/omnibus/settings/database/#upgrade-packaged-postgresql-server).
......@@ -1407,6 +1407,31 @@ Update your API integration to handle the `422` status code when making pipeline
</div>
<div class="deprecation breaking-change" data-milestone="18.0">
### PostgreSQL 14 and 15 no longer supported
<div class="deprecation-notes">
- Announced in GitLab <span class="milestone">17.9</span>
- Removal in GitLab <span class="milestone">18.0</span> ([breaking change](https://docs.gitlab.com/update/terminology/#breaking-change))
- To discuss this change or learn more, see the [deprecation issue](https://gitlab.com/gitlab-org/gitlab/-/issues/521663).
</div>
GitLab follows an [annual upgrade cadence for PostgreSQL](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/data-access/database-framework/postgresql-upgrade-cadence/).
Support for PostgreSQL 14 and 15 is scheduled for removal in GitLab 18.0.
In GitLab 18.0, PostgreSQL 16 becomes the minimum required PostgreSQL version.
PostgreSQL 14 and 15 will be supported for the full GitLab 17 release cycle.
PostgreSQL 16 will also be supported for instances that want to upgrade prior to GitLab 18.0.
If you are running a single PostgreSQL instance you installed by using an Omnibus Linux package, an automatic upgrade may be attempted with 17.11.
Make sure you have enough disk space to accommodate the upgrade. For more information, see the [Omnibus database documentation](https://docs.gitlab.com/omnibus/settings/database/#upgrade-packaged-postgresql-server).
</div>
<div class="deprecation " data-milestone="18.0">
### Project page in group settings is deprecated
......
0% 加载中 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册