Skip to content

ci: run the tests and the development environment on PostgreSQL 18 - #1204

Open
tintinhamans wants to merge 1 commit into
ctrliq:mainfrom
community-outpost:ci/postgresql-18
Open

tintinhamans wants to merge 1 commit into
ctrliq:mainfrom
community-outpost:ci/postgresql-18

Conversation

@tintinhamans

@tintinhamans tintinhamans commented Nov 13, 2026 •

Copy link
Copy Markdown
SUMMARY

The operator deploys PostgreSQL 18, but CI and the dev environment still ran 15. This moves both to 18.

18 can't read a 15 data directory, so the dev database gets a new volume, tools_awx_db_18. If tools_awx_db_15 exists, make docker-compose copies the database over once and leaves the old volume alone. docker-clean-volumes also pointed at tools_awx_db, which no longer exists.

Full API suite and migrations pass locally on 18. I tested the copy against a 15 volume with data in it, including a failed start.

ISSUE TYPE
  • Bug, Docs Fix or other nominal change
COMPONENT NAME
  • Other
ASCENDER VERSION
25.6.4.dev37+gf6d436167

Assisted-by: Claude Opus 5.5

@tintinhamans
tintinhamans marked this pull request as draft November 13, 2026 21:27
The operator deploys PostgreSQL 18, but CI and the development environment
still ran 15. CI's service and the development database move to 18.

PostgreSQL 18 cannot open a data directory written by 15, so the
development database gets a volume of its own, tools_awx_db_18. The first
`make docker-compose` with a tools_awx_db_15 volume copies its database
across with pg_dump and pg_restore (the sclorg 18 image's pg_upgrade only
upgrades from 17) and leaves the old volume as it was. A failed copy
removes the new volume, so the next run tries again.

docker-clean-volumes removed tools_awx_db, a volume that no longer exists;
it now removes tools_awx_db_18 and tools_awx_db_15.

Signed-off-by: tintinhamans <5984296+tintinhamans@users.noreply.github.com>
@tintinhamans
tintinhamans marked this pull request as ready for review November 13, 2026 22:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant