fix: cover pg_cron legacy extversion strings with alignment migration and alias scripts#2300
Draft
brainrake wants to merge 3 commits into
Draft
fix: cover pg_cron legacy extversion strings with alignment migration and alias scripts#2300brainrake wants to merge 3 commits into
brainrake wants to merge 3 commits into
Conversation
… and alias scripts pg_cron installs recorded with old non-canonical extversion strings (e.g. bare "1.6" instead of "1.6.4") have no update path once the package builds moved to a canonical-version chain, so ALTER EXTENSION pg_cron UPDATE fails with: extension "pg_cron" has no update path from version "1.6" to "1.6.4" Add an empty 1.6 -> 1.6.4 alignment migration plus symlinked alias scripts for every other legacy version string (1.0, 1.1, 1.2, 1.3, 1.4, 1.4-1, 1.5), and a nix/ext test mode (testAllUpgradeEdges) that exercises every discovered upgrade edge -- including symlinked aliases and no-op alignment scripts -- not just the canonical chain from versions.json. Supersedes #1790 (rebased onto current develop and squashed into a single commit, dropping unrelated arm64 AMI build/cleanup-script diagnostics that had accumulated in that branch's history). Co-Authored-By: Sam Rose <samuel@supabase.io>
brainrake
force-pushed
the
pg-cron-migration-fix-v2
branch
from
July 22, 2026 02:29
161319a to
bf7d3ef
Compare
PostgreSQL Package Dependency Analysis: PR #2300
SummaryNo packages had MAJOR version updates. Full Analysis ResultsPostgreSQL 15 Dependency ChangesExtracting PostgreSQL 15 dependencies...
Runtime Closure Size
Raw Dependency ClosurePostgreSQL 17 Dependency ChangesExtracting PostgreSQL 17 dependencies...
Runtime Closure Size
Raw Dependency Closure |
PostgreSQL Extension Dependency Analysis: PR #2300
SummaryNo extensions had dependencies with MAJOR version updates. Full Analysis ResultsPostgreSQL 15 Extension DependenciesPostgreSQL 17 Extension DependenciesOrioleDB 17 Extension Dependencies |
This comment has been minimized.
This comment has been minimized.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Supersedes #1790 (rebased onto current
developand squashed into a single clean commit; the original PR's history had accumulated a lot of CI-debugging churn while chasing flaky arm64 test-runner capacity issues).pg_cron--1.6--1.6.4.sqlalignment migration plus symlinked alias scripts for every other legacy/non-canonical extversion string pg_cron has shipped under (1.0,1.1,1.2,1.3,1.4,1.4-1,1.5), restoring a resolvableALTER EXTENSION pg_cron UPDATEpath for projects still recording one of these old version strings.testAllUpgradeEdgesnix/ext test mode that discovers and exercises every upgrade edge on disk (including symlinked aliases and no-op alignment scripts), not just the canonical chain fromversions.json.Root cause / customer impact: supabase/supabase#46669 — in-place PG upgrades fail at the completion step with
extension "pg_cron" has no update path from version "1.6" to "1.6.4"for any project whose pg_cron extension is still recorded at the bare1.6version.Test plan
run-testinfraAMI nix jobs (15/17/orioledb-17, amd64/arm64) — arm64 previously failed on fix: cover the old default value 1.6 (same as 1.6.4) with empty migration #1790 due toInsufficientInstanceCapacity(AWS capacity, not a code issue); re-verify green here.Fixes PSQL-1414
🤖 Generated with Claude Code