For 95% of standard search use cases (text search, typo tolerance, filtering) up to 10M rows, PostgreSQL with this SDK is faster and drastically cheaper. You only need ES if you require complex aggregations or faceted navigation on petabytes of data.

No. The Zombie Query Prevention mechanism uses AbortController. If a fast strategy resolves, slow queries are immediately cancelled via AbortSignal, freeing up DB connections and preventing table locks.

It uses a Smart Hybrid Fallback. If standard FTS fails, it falls back to Trigram fuzzy matching, which natively handles misspellings. It also handles keyboard layout errors (e.g., typing Russian on an English layout) using ISO 9 standardization.

Yes. By installing the pgvector extension and configuring OpenAI/Gemini API keys, the engine can perform vector similarity searches alongside traditional text searches.

Absolutely. The engine uses parameterized queries for all values and a strict SqlSanitizer whitelist for SQL identifiers (tables, columns). Dynamic filter keys are also strictly validated against the configuration.