Skip to content

fix(ci): run the backup restore drill on Postgres 18 - #266

Merged
afeezorobsco-cyber merged 1 commit into
mainfrom
fix/backup-drill-postgres-18
Nov 5, 2026
Merged

afeezorobsco-cyber merged 1 commit into
mainfrom
fix/backup-drill-postgres-18

Conversation

@afeezorobsco-cyber

Copy link
Copy Markdown
Contributor

The backup restore drill has failed since Nov 2 with:

pg_restore: error: could not execute query: ERROR:  unrecognized configuration parameter "transaction_timeout"

GitHub moved ubuntu-latest to an image whose postgresql-client is version 18, while the drill's server was Postgres 16. A newer pg_dump writes SET transaction_timeout, which that server doesn't recognise. PGCLIENT_VERSION: '16' was set but never used.

Changes

  • The drill's server is now Postgres 18, matching the Render database.
  • It installs postgresql-client-${PGCLIENT_VERSION} and puts that version first on PATH.
  • A new step stops with a clear error if the client or server major version differs from PGCLIENT_VERSION.

Not covered: this drill backs up a small seeded test database, so it proves the scripts work. It doesn't back up real data.

The drill is running on this branch to check the fix before merge.

🤖 Generated with Claude Code

The runner's newer pg_dump wrote a setting the drill's Postgres 16 server
rejected on restore. Match the Render database's version, use the declared
client version, and fail clearly if they differ.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown

Malware scan: passed, with notes for the reviewer

Nothing malicious was detected in 8f51e02. These changes touch sensitive areas and should get a careful look before CI is approved:

Where Rule Why
.github/workflows/backup-restore-drill.yml:12 workflow-change Changes a CI workflow; a maintainer must review before approving runs.

@afeezorobsco-cyber
afeezorobsco-cyber merged commit cf7c9d3 into main Nov 5, 2026
3 checks passed
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.

1 participant