Skip to content

Switch to postgres 16 as a minimum requirement#5031

Open
ShimShtein wants to merge 1 commit into
theforeman:masterfrom
ShimShtein:switch_pg13_to_pg16
Open

Switch to postgres 16 as a minimum requirement#5031
ShimShtein wants to merge 1 commit into
theforeman:masterfrom
ShimShtein:switch_pg13_to_pg16

Conversation

@ShimShtein

Copy link
Copy Markdown
Member

What changes are you introducing?

Update the minimum version of PostgreSQL db to 16

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

We are switching from PostgreSQL 13 to 16.

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

Contributor checklists

  • I am okay with my commits getting squashed when you merge this PR.
  • I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

  • Foreman 3.19/Katello 4.21
  • Foreman 3.18/Katello 4.20 (Satellite 6.19)
  • Foreman 3.17/Katello 4.19
  • Foreman 3.16/Katello 4.18 (Satellite 6.18; orcharhino 7.6, 7.7, and 7.8)
  • Foreman 3.15/Katello 4.17
  • Foreman 3.14/Katello 4.16 (Satellite 6.17; orcharhino 7.4; orcharhino 7.5)
  • We do not accept PRs for Foreman older than 3.14.

@github-actions github-actions Bot added Needs tech review Requires a review from the technical perspective Needs style review Requires a review from docs style/grammar perspective Needs testing Requires functional testing labels Jul 8, 2026
@github-actions

github-actions Bot commented Jul 8, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs style review Requires a review from docs style/grammar perspective Needs tech review Requires a review from the technical perspective Needs testing Requires functional testing Not yet reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant