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-07-15 22:59:45 |
Message-ID: | CAPpHfds+2wNNWjpgmDbRxiHf=8jj1yUGM6NWt71eTH-uAkFr-A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Jun 30, 2021 at 1:06 AM Alexander Korotkov <aekorotkov(at)gmail(dot)com> wrote:
> 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.
I got no feedback on this yet. And 14beta3 is approaching...
I'm going to write a patch fixing enforce_generic_type_consistency()
while saving its general logic (as far as I can understand it).
------
Regards,
Alexander Korotkov
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2021-07-16 02:05:00 | Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size |
Previous Message | PG Bug reporting form | 2021-07-15 22:04:41 | BUG #17111: Database created, cannot be created, but reported as inexist |