hermes-memory-pgvector 0.3.0__tar.gz → 0.3.1__tar.gz

{hermes_memory_pgvector-0.3.0 → hermes_memory_pgvector-0.3.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hermes-memory-pgvector
-Version: 0.3.0
+Version: 0.3.1
 Summary: Postgres + pgvector memory provider plugin for hermes-agent. Multi-agent storage layer with per-minion themes, async writer, no LLM in the memory hot path.
 Author: Andrea Borghi
 License: BSD-3-Clause

{hermes_memory_pgvector-0.3.0 → hermes_memory_pgvector-0.3.1}/hermes_memory_pgvector.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hermes-memory-pgvector
-Version: 0.3.0
+Version: 0.3.1
 Summary: Postgres + pgvector memory provider plugin for hermes-agent. Multi-agent storage layer with per-minion themes, async writer, no LLM in the memory hot path.
 Author: Andrea Borghi
 License: BSD-3-Clause

{hermes_memory_pgvector-0.3.0 → hermes_memory_pgvector-0.3.1}/pgvector/__init__.py

@@ -239,6 +239,19 @@ class PgvectorMemoryProvider(MemoryProvider):
             or kwargs.get("agent_identity")  # accept 'default' if nothing else set
             or "default"
         )
+
+        # Re-initialization guard (v0.3.1): one registered provider instance
+        # can have initialize() called again for a new session — the gateway
+        # reuses the registered provider rather than constructing a fresh one
+        # per session. Without tearing down the previous session's writer +
+        # pool first, each re-init abandoned a ConnectionPool whose warm
+        # connection lingered in Postgres until idle_session_timeout — the
+        # v0.3.0 connection leak that saturated the server's slots under a
+        # burst of concurrent sessions. shutdown() is idempotent and drains
+        # in-flight writes, so calling it unconditionally here is safe.
+        if self._store is not None or self._writer is not None:
+            self.shutdown()
+
         self._store = MemoryStore(self._config["dsn"])
         try:
             # Schema is verify-only at runtime — admin applies the

{hermes_memory_pgvector-0.3.0 → hermes_memory_pgvector-0.3.1}/pgvector/plugin.yaml

@@ -1,5 +1,5 @@
 name: pgvector
-version: 0.3.0
+version: 0.3.1
 description: "Postgres + pgvector storage layer for hermes-agent. Mirrors built-in MEMORY.md / USER.md + captures every substantive (user, assistant) chat turn into a conversations table. Per-agent themes (marketing/sales/trading/incident/morning-report/…) via X-Hermes-Session-Key header — every systemd-run minion gets its own scope. 768-dim semantic recall. Async writer + connection pool. No LLM mediation."
 pip_dependencies:
   - "psycopg[binary]>=3.3.4"

{hermes_memory_pgvector-0.3.0 → hermes_memory_pgvector-0.3.1}/pgvector/store.py

@@ -38,16 +38,27 @@ class MemoryStore:
         self,
         dsn: str,
         *,
-        min_size: int = 1,
+        min_size: int = 0,
         max_size: int = 4,
         timeout: float = 5.0,
+        max_idle: float = 30.0,
+        max_lifetime: float = 300.0,
     ):
-        """Open a lazily-initialized ConnectionPool.
-
-        min_size=1 keeps a single warm connection — enough for the agent
-        thread under low traffic. max_size=4 lets the writer thread + a
-        burst of recall calls overlap. Pool is opened on first use (or
-        explicit `open()`) and closed via `close()`.
+        """Open a lazily-initialized, self-draining ConnectionPool.
+
+        min_size=0 means an idle pool holds ZERO connections — critical so
+        a pool that gets abandoned (a re-initialized provider, or a session
+        the gateway never explicitly shuts down) cannot strand a warm
+        backend in Postgres until the server's idle_session_timeout reaps
+        it. Under load the pool still grows to max_size=4 so the agent
+        thread and the async-writer drain thread can overlap.
+
+        max_idle (30s) closes connections returned to the pool that then sit
+        unused, shrinking back toward min_size. max_lifetime (300s) caps the
+        absolute age of any pooled connection. Together these keep the
+        connections "short-lived when idle, pooled under load" and bound the
+        plugin's Postgres footprint to actual concurrent demand rather than
+        to the number of sessions ever opened.
         """
         self._dsn = dsn
         self._lock = threading.Lock()
@@ -55,6 +66,8 @@ class MemoryStore:
         self._min_size = min_size
         self._max_size = max_size
         self._timeout = timeout
+        self._max_idle = max_idle
+        self._max_lifetime = max_lifetime
 
     # -- Pool lifecycle ------------------------------------------------------
 
@@ -69,6 +82,8 @@ class MemoryStore:
                     min_size=self._min_size,
                     max_size=self._max_size,
                     timeout=self._timeout,
+                    max_idle=self._max_idle,
+                    max_lifetime=self._max_lifetime,
                     open=True,
                     name="pgvector-memory",
                 )

{hermes_memory_pgvector-0.3.0 → hermes_memory_pgvector-0.3.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "hermes-memory-pgvector"
-version = "0.3.0"
+version = "0.3.1"
 description = "Postgres + pgvector memory provider plugin for hermes-agent. Multi-agent storage layer with per-minion themes, async writer, no LLM in the memory hot path."
 readme = "README.md"
 requires-python = ">=3.11"