Horton

Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Korotkov <aekorotkov@gmail.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Neil Chen <carpenter.nail.cz@gmail.com>, Alexander Law <exclusion@gmail.com>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>, Paul A Jungwirth <pj@illuminatedcomputing.com>
Date: 2021-07-27T15:38:07Z
Lists: pgsql-bugs 
Alexander Korotkov <aekorotkov@gmail.com> writes:
> On Wed, Jul 21, 2021 at 12:54 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> In any case, apologies for taking so long to get back to this.  Here's
>> a proposed patch (based in part on Neil's earlier patch).

> This patch looks good to me.  Besides fixing the particular bug
> report, it seems that the situation of mismatching range and
> multirange types in arguments is now handled correctly.

Thanks for reviewing!  I'll push it later today.

			regards, tom lane

Commits

  1. Fix bugs in polymorphic-argument resolution for multiranges.

  2. Fixes for multirange selectivity estimation