Update to my recent article about performance issues with prepared queries in postgresql:

It came to my attention that you can give the prepare: :unnamed option to your Ecto database configuration to achieve a similar effect on Postgres versions before 12. This works universally, but it only gives you about 80% of the performance of the force_custom_plan option in my testing, presumably because we lose the performance boost that skipping the parsing step for prepared queries gives us.