Re: BUG #15890: Planner can't use index "(col) where col is not null"for query "where col in ($1, $2, ... $100+)"

On Wed, 3 Jul 2019 at 21:42, PG Bug reporting form
<noreply@postgresql.org> wrote:
> -- 100+ elements, can't use index, using seq scan
> # explain select a from test_not_null_indexes where a in

> Is it possible somehow to pass information that (a) can't be null in such
> cases?

Yes, it is possible, however, this is not a bug in v11. It's something
that has been improved in v12, which will be released later this year.

See: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=65ce07e020

v11 won't receive the same improvement.

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services