Skip to content

Fix data loss by adding checkpoint after vector index creation #422

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jfrench9 merged 1 commit into from
Mar 3, 2026
Merged

Fix data loss by adding checkpoint after vector index creation #422

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions robosystems/graph_api/routers/databases/tables/materialize.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -399,6 +399,11 @@ async def materialize_table(
# Must happen AFTER data is loaded (indexes on empty tables are empty)
ladybug_service.db_manager.create_vector_index(conn, table_name)

# Checkpoint again to persist vector index to disk
# Without this, the index exists only in-memory and is lost when
# force_database_cleanup destroys the Database object below
conn.execute("CHECKPOINT")

# Release buffer pool memory - data is safe on disk now
ladybug_service.db_manager.connection_pool.force_database_cleanup(
graph_id, aggressive=True
Expand Down