Structural comparison in pg-upgrade-test (both twin databases) - #38
Closed
jnasbyupgrade wants to merge 1 commit into
Closed
Structural comparison in pg-upgrade-test (both twin databases)#38jnasbyupgrade wants to merge 1 commit into
jnasbyupgrade wants to merge 1 commit into
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
3 tasks
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
jnasbyupgrade
marked this pull request as draft
August 4, 2026 21:11
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
from
August 4, 2026 23:17
8f0a273 to
e74ffc6
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 5, 2026 18:14
6146766 to
c41e8f5
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
2 times, most recently
from
August 5, 2026 19:40
a545c66 to
a21fd53
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
2 times, most recently
from
August 5, 2026 19:57
30073d0 to
1ff9811
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
2 times, most recently
from
August 5, 2026 21:45
e0fb0d2 to
80b0215
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 5, 2026 22:49
6277cd3 to
7ce4954
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
from
August 5, 2026 22:49
80b0215 to
49875be
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 5, 2026 23:00
7ce4954 to
73ce64e
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
from
August 5, 2026 23:00
49875be to
ea5f6b5
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 5, 2026 23:11
73ce64e to
1858473
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
2 times, most recently
from
August 5, 2026 23:16
d0cb6de to
d0d0dd9
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 6, 2026 18:05
1a11083 to
bd14a70
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
from
August 6, 2026 18:05
d0d0dd9 to
89db338
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 6, 2026 18:54
bd14a70 to
4008107
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
from
August 6, 2026 18:54
89db338 to
45ee2d4
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 6, 2026 19:04
4008107 to
00371d9
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
from
August 6, 2026 19:04
45ee2d4 to
93b075a
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 6, 2026 19:16
00371d9 to
c8bf327
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
from
August 6, 2026 19:16
93b075a to
d19c5ac
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 6, 2026 20:57
c8bf327 to
aed095e
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
from
August 6, 2026 20:57
d19c5ac to
eed3319
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 6, 2026 21:24
aed095e to
019e3ee
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
from
August 6, 2026 21:25
eed3319 to
9dbbc9d
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 6, 2026 21:29
019e3ee to
5a9fde3
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
from
August 6, 2026 21:29
9dbbc9d to
3b09aa5
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 6, 2026 22:13
5a9fde3 to
449633a
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
from
August 6, 2026 22:14
3b09aa5 to
73f309f
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 6, 2026 22:51
449633a to
0211525
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
from
August 6, 2026 22:51
73f309f to
c303d3f
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 6, 2026 22:56
0211525 to
ae463a2
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
from
August 6, 2026 22:56
c303d3f to
1f11c1a
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 9, 2026 18:50
ae463a2 to
1a833cd
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
from
August 9, 2026 19:59
1f11c1a to
7d20c0d
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 9, 2026 20:19
1a833cd to
ffe07ed
Compare
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
from
August 9, 2026 20:21
7d20c0d to
8e67619
Compare
jnasbyupgrade
force-pushed
the
phase6-compare-and-report
branch
from
August 9, 2026 20:27
ffe07ed to
b1bc394
Compare
…de-test Adds an EXISTING_DB argument to bin/compare_fresh_vs_update so it can structurally diff an already-populated database against a fresh install, instead of only ever creating+updating its own scratch database - lets callers that produced their update/upgrade result some other way (here, bin/test_existing's real binary pg_upgrade path) reuse the same comparison without this script re-deriving that database itself. Since EXISTING_DB was installed independently (its own call to test/helpers/create_test_schema.sql, generating its own random schema name), the fresh install this script creates for the comparison discovers and reuses THAT schema rather than generating a new one, so both sides still land in the same schema - same requirement, and same reasoning, as the shared-schema design bin/compare_fresh_vs_update's scratch-vs-scratch mode already uses. Wires this into the pg-upgrade-test CI job: after run-suite proves both twin databases (upgrade_oldest_first, upgrade_current_first - one per update-vs-pg_upgrade ordering) are at the current version, each is now also structurally compared against a fresh install, catching a divergence class the fixed pgTAP suite doesn't - an object left subtly different (body, comment, ACL) by surviving a real binary catalog migration, as opposed to only an in-place ALTER EXTENSION UPDATE (which the test job's own update leg already covers with the same tool). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
jnasbyupgrade
force-pushed
the
phase6b-compare-in-pg-upgrade-test
branch
from
August 9, 2026 20:30
8e67619 to
9a3b43d
Compare
Contributor
Author
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
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.
Extends
bin/compare_fresh_vs_updatewith anEXISTING_DBargument so it can structurally diff an already-populated database against a fresh install, instead of only ever creating and updating its own scratch database. This letspg-upgrade-test's twin databases (upgrade_oldest_first/upgrade_current_first, migrated by a real binarypg_upgrade) reuse the same comparison tool thetestjob's update leg already uses, rather than duplicating that logic.Since
EXISTING_DBwas installed independently (its own call totest/helpers/create_test_schema.sql, generating its own random schema), the fresh install this script creates for the comparison discovers and reuses that same schema instead of generating a new one - both sides still need to land in the same schema for the comparison to isolate real divergence rather than a spurious schema-name difference.pg-upgrade-test's CI job now runs this comparison against both twin databases right afterrun-suiteconfirms they're at the current version, catching a divergence class the fixed pgTAP suite doesn't: an object left subtly different (body, comment, ACL) by surviving a real catalog migration, as opposed to only an in-placeALTER EXTENSION UPDATE.