365fa3ce50
On managed PostgreSQL services (e.g. Azure Flexible Server), the pg_trgm extension may not be available, causing two failures: 1. Migration c1a2b3d4e5f6 crashes on CREATE EXTENSION 2. Even if migration is bypassed, the default 'trigram' entity lookup strategy uses the % operator which requires pg_trgm, causing retain background tasks to fail silently Changes: - Migration now gracefully skips pg_trgm and index creation if the extension cannot be loaded - EntityResolver auto-detects pg_trgm availability on first use and falls back to 'full' lookup strategy with a warning log Co-authored-by: coder999999999 <coder999999999@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| versions | ||
| env.py | ||
| README | ||
| script.py.mako | ||
Generic single-database configuration.