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

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: alexey(dot)ermakov(at)dataegret(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15890: Planner can't use index "(col) where col is not null" for query "where col in ($1, $2, ... $100+)"
Date: 2019-07-03 13:01:41
Message-ID: CAKJS1f8D_DvOZeOaOFTT9Z_HptRTVHmFB8BnOsWM9ZYN2zq3eA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, 3 Jul 2019 at 21:42, PG Bug reporting form
<noreply(at)postgresql(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Maarten Jacobs 2019-07-03 13:44:58 Cannot alter columns and add constraints in one alter statement since 11.4 update
Previous Message Michael Paquier 2019-07-03 11:35:51 Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows