This lets us: - avoid issues with broken hash indices for PostgreSQL <10 - drop runtime checks and legacy codepaths for <11 in db search - always enable custom query plans for performance optimisation PostgreSQL 11 is already EOL since 2023-11-09, so in theory everyone should already have moved on to 12 anyway. |
||
|---|---|---|
| .. | ||
| database_search_test.exs | ||
| elasticsearch_test.exs | ||
| meilisearch_test.exs | ||