fix(memory): sync new memories into pgvector
Memind CI / Test, build, and release guards (push) Successful in 2m31s
Memind CI / Test, build, and release guards (push) Successful in 2m31s
This commit is contained in:
@@ -394,6 +394,14 @@ Optional table name for pgvector retrieval. Defaults to `memory_embeddings`.
|
||||
|
||||
Optional PostgreSQL pool size for Memory V2 pgvector retrieval. Defaults to `5`.
|
||||
|
||||
`MEMORY_PGVECTOR_SYNC_USER_LIMIT`
|
||||
|
||||
Maximum number of recent active memories synchronously upserted for the current
|
||||
user after a successful `write(...)`, `compact(...)`, or candidate promotion.
|
||||
Defaults to `50`. When a session ID is available the sync is additionally scoped
|
||||
to that session. This immediate, idempotent sync keeps newly saved memories
|
||||
recallable without waiting for the separate global checkpoint backfill.
|
||||
|
||||
## Current Integration Points
|
||||
|
||||
Memory V2 is only allowed to sit above existing memory code.
|
||||
|
||||
Reference in New Issue
Block a user