Skip to content
Changelog

Tune page search per knowledge base with PageSearchConfig

ContributorAshpreet BediFounder & CEO

September 8, 20261 min read

Pass Agno's PageSearchConfig to Knowledge(page_search=...) to set plan caching, sequential scans, parallel costs and worker counts as typed PostgreSQL planner fields. The planner settings that suit page search on one knowledge base don't have to suit the rest of your database.

from agno.knowledge import Knowledge
from agno.knowledge.page import PageSearchConfig
 
knowledge = Knowledge(
    name="docs",
    vector_db=vector_db,
    page_search=PageSearchConfig(enable_seqscan=False, max_parallel_workers_per_gather=0),
)

Agno applies these settings inside each search transaction and nowhere else. Any value you leave unset inherits the PostgreSQL setting.

See the PageSearchConfig reference for every field and its default.

Frequently asked questions

Pass page_search=PageSearchConfig(...) to Knowledge. PageSearchConfig covers plan caching, sequential scans, parallel costs and worker counts for that knowledge base only.

No. Agno applies PageSearchConfig inside each page search transaction and nowhere else. Unset fields fall back to the database setting in PostgreSQL.

See the PageSearchConfig reference in the Agno documentation.

Shipped around the same time