Hello! I have a query on a large table that is very fast (0s): https://gist.github.com/collimarco/039412b4fe0dcf39955888f96eff29db#file-fast_query-txt
Basically the query matches the rows that have a tag1 OR tag2 OR tag3 OR tag4 OR tag5... However if you increase the number of OR at some point PostgreSQL makes the bad decision to change its query plan! And the new plan makes the query terribly slow: https://gist.github.com/collimarco/039412b4fe0dcf39955888f96eff29db#file-slow_query-txt Instead of this (which is fast): Bitmap Index Scan on index_subscriptions_on_project_id_and_tags It starts using this (which is slow): Parallel Index Scan using index_subscriptions_on_project_id_and_created_at The choice seems quite stupid since it doesn't have the tags on the new index... and indeed the query takes about 1 minute instead of a few milliseconds. Here's a list of the available indexes: https://gist.github.com/collimarco/039412b4fe0dcf39955888f96eff29db#file-_indexes-txt How can I encourage PostgreSQL to use the Bitmap Index Scan even when there are many OR conditions? I have tried with VACUUM ANALYZE subscriptions but it doesn't help. Note: the query is generated dynamically by customers of a SaaS, so I don't have full control on it Thank you very much for any advice! Marco Colli
