Skip to content

feat: Add PostgreSQL 18 support#90

Open
ZPascal wants to merge 2 commits into
cloudfoundry:mainfrom
ZPascal:add-postgresql-18-support
Open

feat: Add PostgreSQL 18 support#90
ZPascal wants to merge 2 commits into
cloudfoundry:mainfrom
ZPascal:add-postgresql-18-support

Conversation

@ZPascal
Copy link
Copy Markdown
Contributor

@ZPascal ZPascal commented Mar 31, 2026

  • Add Pg 18 support

Should be discussed:
Should we add PG 18 as default version?

Alphasite
Alphasite previously approved these changes Apr 1, 2026
Copy link
Copy Markdown
Contributor

@Alphasite Alphasite left a comment

Choose a reason for hiding this comment

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

I think this looks good to me. it looks similar to the other versions

@ZPascal
Copy link
Copy Markdown
Contributor Author

ZPascal commented Apr 1, 2026

@Alphasite Should we replace the default version to PG 18?

@Alphasite
Copy link
Copy Markdown
Contributor

Alphasite commented Apr 1, 2026

I think that’s reasonable. We’d probably want to also add it to BBR if we did that then? Chris, Colin and I just added PG 15, 16 and 17. 18 also seems reasonable.

@ZPascal
Copy link
Copy Markdown
Contributor Author

ZPascal commented Apr 1, 2026

I think that’s reasonable. We’d probably want to also add it to BBR if we did that then? Chris, Colin and I just added PG 15, 16 and 17. 18 also seems reasonable.

Hi @Alphasite, I also prefer it, but we should release it as a new major release.

We’d probably want to also add it to BBR if we did that then? Chris, Colin and I just added PG 15, 16 and 17. 18 also seems reasonable.

The BBR job already supports PG 15,16 and 17, and I've also replaced the default version to 18 inside the BBR job.

@Alphasite
Copy link
Copy Markdown
Contributor

did you want to merge this version?

@ZPascal
Copy link
Copy Markdown
Contributor Author

ZPascal commented Apr 10, 2026

@Alphasite, I think we should first remove PG 11 and 13 from the release before we add a new version.

@ZPascal
Copy link
Copy Markdown
Contributor Author

ZPascal commented May 13, 2026

@colins Can you please check the PR?

Alphasite
Alphasite previously approved these changes May 13, 2026
Copy link
Copy Markdown
Contributor

@Alphasite Alphasite left a comment

Choose a reason for hiding this comment

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

I think it looks ok. I’m assuming it all compiles?

@github-project-automation github-project-automation Bot moved this from Inbox to Pending Merge | Prioritized in Foundational Infrastructure Working Group May 13, 2026
@ZPascal
Copy link
Copy Markdown
Contributor Author

ZPascal commented May 13, 2026

I think it looks ok. I’m assuming it all compiles?

Yes, but let me verify it on a Noble image. We've faced a few issues this week on Ubuntu 26.04.

ZPascal added 2 commits May 13, 2026 23:11
# Conflicts:
#	ci/pipeline.yml
#	jobs/bbr-postgres-db/spec
#	jobs/postgres/spec
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds PostgreSQL 18 as a new packaged major version in this BOSH release, updates version-selection defaults/docs, and extends the CI pipeline to track/bump the new upstream source.

Changes:

  • Add a new postgres-18 package (spec + packaging script) to build from upstream postgresql-18.*.tar.gz.
  • Update job specs and the used_postgresql_versions.yml mapping to include Postgres 18 and set the default major version to 18.
  • Extend the Concourse pipeline to fetch and bump the Postgres 18 source tarball.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 5 comments.

Show a summary per file
File Description
README.md Updates documented default PostgreSQL major version and supported versions list.
packages/postgres-18/spec Declares the new Postgres 18 source blob pattern.
packages/postgres-18/packaging Adds build script for compiling/installing Postgres 18.
jobs/postgres/templates/used_postgresql_versions.yml Adds Postgres 18 version mapping and changes default major version.
jobs/postgres/spec Includes postgres-18 package and changes the default databases.version.
jobs/bbr-postgres-db/spec Includes postgres-18 package and changes the default postgres.version.
ci/pipeline.yml Adds postgres-18-src resource and a bump task for Postgres 18.
Comments suppressed due to low confidence (1)

jobs/postgres/templates/used_postgresql_versions.yml:7

  • The 17 minor version is set to 17.4, but the repo’s current blob is postgres/postgresql-17.9.tar.gz (see config/blobs.yml). This mismatch can cause the release to reference a PostgreSQL version that isn’t available as a blob. Update used_postgresql_versions.yml to match the blob version (or add the corresponding blob) and remove the conflicting 17 entry.
    17:
      minor_version: "17.4"

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread README.md
Property | Description
-------- | -------------
databases.version | Define the used PostgreSQL major version. Default: 16
databases.version | Define the used PostgreSQL major version. Default: 18. Supported versions: 13, 15, 16, 17, 18
Comment thread jobs/bbr-postgres-db/spec
@@ -49,5 +50,5 @@ properties:
default: false
description: "uses singele transaction when restoring databases"
Comment on lines +2 to +5
default: 18
major_version:
18:
minor_version: "18.2"
Comment thread ci/pipeline.yml
secret_access_key: ((postgres-release-blobstore-user.password))
- task: bump-postgres-18-package
file: postgres-release/ci/tasks/bump-postgres-packages/task.yml
image: bosh-cli-registry-image
Comment thread ci/pipeline.yml
Comment on lines +105 to +113
- task: bump-yq-package
file: postgres-release/ci/tasks/bump-yq-packages/task.yml
image: bosh-integration-image
params:
PRIVATE_YML: |
blobstore:
options:
access_key_id: ((postgres-release-blobstore-user.username))
secret_access_key: ((postgres-release-blobstore-user.password))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Pending Merge | Prioritized

Development

Successfully merging this pull request may close these issues.

3 participants