[31groot]

Related Issues

• fixes Support zero-downtime vectorization on PgvectorDocumentStore #1696

Proposed Changes

• Add synchronous and asynchronous helpers for replacing an existing Pgvector document table with a staging table.
• Validate table identifiers, database and schema compatibility, and table structure before performing the replacement.
• Rename indexes during the cutover to support the staging table becoming the active table.
• Retain the previous active table as a backup rather than dropping it immediately.
• Add tests covering successful replacement, missing staging tables, existing backup tables, and incompatible table configurations.
• Update the relevant docstrings to document the new functionality and its usage.

The goal is to reduce downtime when replacing Pgvector tables while preserving the previous table as a backup.

Limitation: Writers should be paused during the cutover. This implementation reduces replacement downtime but does not guarantee uninterrupted concurrent writes.

How did you test it?

Ran the following commands from integrations/pgvector with a local Pgvector PostgreSQL instance:

• hatch run fmt src/haystack_integrations/document_stores/pgvector/table_replacement.py tests/test_table_replacement.py
• hatch run fmt-check src/haystack_integrations/document_stores/pgvector/document_store.py src/haystack_integrations/document_stores/pgvector/table_replacement.py tests/test_table_replacement.py
• hatch run test:integration tests/test_table_replacement.py — 5 passed
• hatch run test:integration tests/test_document_store.py — 57 passed, 2 skipped
• hatch run test:integration tests/test_document_store_async.py — 53 passed, 2 skipped
• hatch run test:types — passed
• git diff --check — passed

Notes for the reviewer

• The previous table is retained as a backup after replacement.
• The replacement helpers support both synchronous and asynchronous usage.
• Please review the transactional cutover, index renaming, validation, and backup-table behavior.
• Writers must be paused during the cutover; uninterrupted concurrent writes are not guaranteed.

Checklist

• I have read the [contributors guidelines](https://github.com/deepset-ai/haystack-core-integrations/blob/main/CONTRIBUTING.md) and the [code of conduct](https://github.com/deepset-ai/haystack-core-integrations/blob/main/CODE_OF_CONDUCT.md).
• I have updated the related issue with new insights and changes.
• I added tests and updated the docstrings.
• I've used a conventional commit type for my PR title: feat:.

[github-actions]

Coverage report (pgvector)

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
integrations/pgvector/src/haystack_integrations/document_stores/pgvector
document_store.py
table_replacement.py					144-145, 265-372, 394-508
Project Total

This report was generated by python-coverage-comment-action

[github-actions]

Coverage report (supabase)

This PR does not seem to contain any modification to coverable code.

[github-actions]

Coverage report (alloydb)

This PR does not seem to contain any modification to coverable code.