Repository navigation
Document 26.10.0 namespace safety and vector-search evaluation - #342
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.
The namespace example reused document IDs across scopes, which 26.10.0 now rejects. Give each scope distinct IDs and document the upgrade behavior, whole-batch rollback, unchanged global ID constraint, and application authorization responsibilities. Link release checksums from installation instructions.
Publish the pg_vectorsearch evaluation and its limitations: pgvector/HNSW remains supported, and PRISM did not qualify for adoption. Correct the PR badge selector and add release and documentation workflow badges to the README. This changes documentation only; package version and published 26.10.0 assets remain unchanged.
Validation: 2,519 tests passed with 32 nightly tests deselected against the isolated native PostgreSQL fixture; pre-commit, Ruff, Pyright, brand asset checks, strict MkDocs build, link checks, and browser rendering of all 56 Mermaid diagrams passed. Independent review verified reported measurements against the accepted benchmark data, executed namespace examples, and checked new anchors and remote badge/checksum URLs. CI provides the separate standard PostgreSQL 16 integration check.