Repository navigation
Conversation
seems the sitemap schema is not supported by mbslave and not included in `mbslave.replication.create_schemas`
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (20)
💤 Files with no reviewable changes (7)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe schema 32 release removes old editor-name objects, adds indexes, and replaces the ChangesSchema 32 release
Priority: ⬇️ Low Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Other Merge Risk: ⚪ Minimal · up to The schema 32 changes are consistent with the documented upgrade path, including intentionally excluding unsupported sitemap migrations. No actionable merge-blocking risk is established; merge after normal checks. Security Architecture ReviewSecurity architecture risk: 🔵 Low · up to The reviewed changes are bounded to an operator-managed database replica. The migration is transactional, the relationship view preserves its columns, and current editor-name uniqueness remains enforced. No introduced security vulnerability was established, but deployed permissions, external consumers, and custom writable deployments remain unverified. Retained concerns Security review detailsSecurity Blast Radius
Trust Boundaries and Controls
Hardening Proposals
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
| DROP TABLE IF EXISTS old_editor_name CASCADE; | ||
|
|
||
| -------------------------------------------------------------------------------- | ||
| /* disabled sitemaps schema related updates, as this seems not to be installed with mbdata |
There was a problem hiding this comment.
migration fails with
running the upgrade fails with
20260602-new-sitemaps-indexes.sql
(1 row)
psql:/tmp/tmpz8yymk5b.sql:22: ERROR: schema "sitemaps" does not exist
as we don't install this schema in mbslave.replication.create_schemas
this updates to the newest schema released 2026-09-21
see https://blog.metabrainz.org/2026/09/21/musicbrainz-server-update-2026-09-21/ for details.
note that i had to comment out migrations for the sitemaps schema as we don't install this in mbslave (see separate commit)
update:
our replications failed with an error
psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "recording_tag_pkey"and i thought the schema update caused the error.turned out we were using an outdated version of mbslave that did not
DISABLE TRIGGERon imports.as of today (2026-10-02 the replication packages still have
SCHEMA_SEQUENCEset to31so updating the database as suggested in this readme would fail withso for the time being, better not merge this. but maybe keep the pr open until musicbrainz starts to send replication packages with the updated schema version.