Weblate full‑text search startup failure with PostgreSQL versions older than 9.6

The goal is to determine whether Weblate 4.10 and later apply the PostgreSQL 9.6+ requirement for the pg_trgm‑based full‑text search uniformly across all supported deployment methods, particularly Docker images, and what the exact behavior is when the requirement is not met.

Uncertainty remains about whether the hard failure is triggered identically in containerized setups, if any configuration option can downgrade the check to a warning, and whether administrators running on PostgreSQL 9.5 have a documented path to retain limited search functionality without upgrading the database.

Does the startup validation that blocks Weblate 4.10+ on PostgreSQL < 9.6 execute the same way in Docker containers as in bare‑metal installations?

Is there a configuration flag or environment variable that can convert the hard failure into a warning while keeping the search endpoint operational?

For administrators unable to upgrade PostgreSQL immediately, what fallback or degraded search mode, if any, is officially supported?