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

From Alexey Ermakov
Subject Re: BUG #15890: Planner can't use index "(col) where col is not null"for query "where col in ($1, $2, ... $100+)"
Date
Msg-id 5D1CB271.6060108@dataegret.com
Whole thread Raw
In response to Re: BUG #15890: Planner can't use index "(col) where col is not null"for query "where col in ($1, $2, ... $100+)"  (David Rowley <david.rowley@2ndquadrant.com>)
List pgsql-bugs
great, thank you!

--
Alexey Ermakov

On 7/3/19 19:01, David Rowley wrote:
> 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.
>




pgsql-bugs by date:

Previous
From: Maarten Jacobs
Date:
Subject: Cannot alter columns and add constraints in one alter statement since11.4 update
Next
From: PG Bug reporting form
Date:
Subject: BUG #15891: Cannot alter columns and add constraints in one alter statement since 11.4 update