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

From: Alexey Ermakov <alexey(dot)ermakov(at)dataegret(dot)com>
To: David Rowley <david(dot)rowley(at)2ndquadrant(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:49:37
Message-ID: 5D1CB271.6060108@dataegret.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(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.
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2019-07-03 14:04:04 BUG #15891: Cannot alter columns and add constraints in one alter statement since 11.4 update
Previous Message Maarten Jacobs 2019-07-03 13:44:58 Cannot alter columns and add constraints in one alter statement since 11.4 update