Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update postgres docker to 16 #351

Merged
merged 11 commits into from
Nov 30, 2023
Merged

chore: update postgres docker to 16 #351

merged 11 commits into from
Nov 30, 2023

Conversation

SamuelBrucksch
Copy link
Contributor

Apparantly permission rules changed with postgres 16. This makes it work again, but as i'm no expert, I can't say for sure this is the right solution.

@SamuelBrucksch SamuelBrucksch changed the title Chore: update postgres to 16 chore: update postgres to 16 Nov 21, 2023
@SamuelBrucksch SamuelBrucksch changed the title chore: update postgres to 16 chore: update postgres docker to 16 Nov 21, 2023
@SamuelBrucksch SamuelBrucksch marked this pull request as ready for review November 21, 2023 14:18
@@ -3,7 +3,7 @@ version: '3.1'

services:
db:
image: postgres:15-alpine
image: postgres:16-alpine
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
image: postgres:16-alpine
image: postgres:alpine

Copy link
Contributor

@BobdenOs BobdenOs Nov 22, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As you can see in this PR it is not always compatible to take the latest version. So please keep the exact version in the PRs. To keep the builds reproducible.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additionally in production they latest version is still 13. So there is no rush to test using the latest and greatest version.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also fine for me.
I ask myself whether we should use the "latest" version on BTP instead?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do think that the productive Postgres version should be tested. Whether that is in additional to the latest version or instead of the latest version is both fine with me. The advantage of also testing the latest version would give a timely heads up for things breaking in the future (around 2-3 years warning period).

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on the documentation page for Parameters for the PostgreSQL on SAP BTP, Hyperscaler Option, the latest available version is 14. So I would think the tests should run with 14, 15 and 16.

Co-authored-by: Johannes Vogel <31311694+johannes-vogel@users.noreply.github.com>
postgres/pg-stack.yml Outdated Show resolved Hide resolved
@johannes-vogel
Copy link
Contributor

I've created a BLI internally for adding the additional voter.

@johannes-vogel johannes-vogel enabled auto-merge (squash) November 30, 2023 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants