Postgres explain plan is not correctly optimezed if the data is a "double" but the collumn is a "numeric"

I opened a pull request on the postgres jdbc, because the execution plan could be false when calculating, leading to performance issues.

There's more on the subject here : https://github.com/pgjdbc/pgjdbc/pull/3285

thank you in advance

Charles