# Tune page search per knowledge base with PageSearchConfig

> Agno's PageSearchConfig sets PostgreSQL planner options for one knowledge base's page search, scoped to its own search transactions. Unset values inherit the database setting.

- Published: 2026-09-08
- Author: Ashpreet Bedi
- Categories: Changelog
- Canonical: https://www.agno.com/articles/tune-page-search-per-knowledge-base-with-pagesearchconfig
- Markdown: https://www.agno.com/articles/tune-page-search-per-knowledge-base-with-pagesearchconfig.md

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.

```python
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](https://docs.agno.com/reference/knowledge/pages#pagesearchconfig) for every field and its default.