Fix tenant manifest addressing and concurrent migrations - #1
Merged
Merged
Conversation
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.
Tenant bindings now carry explicit path-style S3 addressing into the manifest store, preserving virtual-host addressing by default. Blob index migrations use a transaction-scoped advisory lock per schema so simultaneous gateway startups cannot race PostgreSQL catalog creation. The gateway and edge Dockerfiles pin their existing base images by digest.
Validation: Go race tests passed for pgindex, tenantbind, tenantconfig and all blobgw-edge packages. All 18 pgindex tests also passed against a disposable PostgreSQL 17 database, including 12 simultaneous migrations, existing-row preservation, lock cancellation and retry.