From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg12 release notes |
Date: | 2019-05-10 03:57:11 |
Message-ID: | CAKJS1f-Gi=bre2n3FiCkCk05CjBb+PgmsxgY30bEtvh7MNwPsw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 10 May 2019 at 15:45, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> <!--
> Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> 2019-02-20 [e04a3905e] Improve planner's understanding of strictness of type co
> -->
>
> <para>
> Allow IS NOT NULL with mis-matching types to use partial indexes more frequently (Tom Lane)
> </para>
>
> > If so, I think James Coleman should be the author.
>
> ... and yeah, James should get the credit. But there's more wrong with
> the summary than that, because I don't think this was about mismatched
> types particularly. The real motivation was to avoid failing to prove
> the usability of WHERE-x-IS-NOT-NULL partial indexes for IN clauses with
> more than 100 elements.
I think you might be mixing up two items. I'm talking about:
<para>
Allow IN comparisons with arrays to use <literal>IS NOT NULL</literal>
partial indexes more frequently (Tom Lane)
</para>
to which the sgml references 65ce07e02.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-05-10 04:02:11 | Re: pg12 release notes |
Previous Message | Amit Langote | 2019-05-10 03:45:54 | Re: pg12 release notes |