| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Neil Chen <carpenter(dot)nail(dot)cz(at)gmail(dot)com>, Alexander Law <exclusion(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
| Subject: | Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange |
| Date: | 2021-06-29 22:06:34 |
| Message-ID: | CAPpHfduOx3UgF1fmThMj8XrgDhsxxE1DWAF4oR6z2EeVJ+PVtQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Jun 24, 2021 at 2:35 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Alexander Korotkov <aekorotkov(at)gmail(dot)com> writes:
> > I really appreciate a hint here.
>
> I think I'm to blame for most of that code originally, so I'll take
> a look soon. Been up to my neck in other stuff recently.
Do I understand correctly that enforce_generic_type_consistency() is
called only after check_generic_type_consistency() returned true?
If so, that means some of the checks are redundant. Therefore, we can
replace ereport()'s with Assert()'s.
------
Regards,
Alexander Korotkov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-06-30 06:09:48 | BUG #17077: about three parameters in postgresql 13.3 |
| Previous Message | Alexander Korotkov | 2021-06-29 20:22:27 | Re: BUG #17066: Cache lookup failed when null (unknown) is passed as anycompatiblemultirange |