Bump PostgreSQL to version 17.11

What does this MR do?

Bump PostgreSQL to version 17.11

  • Updates PostgreSQL to version 17.11.

Changelog: changed

Signed-off-by: Alec Xu axu@gitlab.com

Risk: Low. Minor release on the same major version, so no pg_upgrade is involved; the postmaster picks up the new binaries on restart after gitlab-ctl reconfigure.

Relates to https://gitlab.com/gitlab-org/omnibus-gitlab/-/work_items/10055

Backports

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • MR title and description are up to date, accurate, and descriptive.
  • MR targets the appropriate branch.
  • Component test plan copied into MR description. (No test plan file exists for PostgreSQL; the checks below cover the change.)
  • Latest merged results pipeline is green.
  • When ready for review, MR is labeled workflowready for review per the Distribution MR workflow.
  • Ensure the equivalent update for Cloud Native GitLab exists. (Not applicable: CNG ships PostgreSQL 18.6 client tools only.)
  • UBT version and corresponding checksum hash have been updated and referenced in the merge request if applicable. (Blocked: no postgresql-all 17.11 bundle in the UBT registry yet.)
    • UBT EE pipeline (Trigger:ee-package-ubt) is green

For GitLab team members

If you don't have permissions to trigger pipelines for this MR, the reviewer should trigger these jobs for you during the review process.

  • The manual Trigger:ee-package jobs have a green pipeline running against latest commit. To debug QA failures, refer to Investigate QA failures.
  • If config/software or config/patches directories are changed, build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
  • If you are changing anything SSL related, the Trigger:package:fips manual job within the Trigger:ee-package downstream pipeline succeeded.
  • If CI/CD configuration is changed, the branch is pushed to dev.gitlab.org to confirm regular branch builds aren't broken.

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes.
  • Documentation created or updated. (Not applicable: version pin only.)
  • Tests added. (Not applicable: version pin only.)
  • Integration tests added to GitLab QA. (Not applicable.)
  • Equivalent MR/issue for the GitLab Chart opened. (Not applicable: the chart does not bundle a PostgreSQL server.)
  • Potential values for new configuration settings validated. (Not applicable: no new settings.)

Test plan

  • build-package-on-all-os in the Trigger:ee-package downstream pipeline succeeds.
  • qa-subset-test passes for EE and CE.
  • On an upgraded node, /opt/gitlab/embedded/bin/psql --version reports 17.11 and gitlab-ctl reconfigure and gitlab-rake gitlab:check complete without errors.
Edited by Jon Doveston

Merge request reports

Loading
Loading