Re: BUG #17066: Cache lookup failed when null (iso-8859-1) is passed as anycompatiblemultirange
От | Alexander Korotkov |
---|---|
Тема | Re: BUG #17066: Cache lookup failed when null (iso-8859-1) is passed as anycompatiblemultirange |
Дата | |
Msg-id | CAPpHfdtgd42dTehaiPqqP7v978oGSFHjLo_3=D_=UWzFTSwOrg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #17066: Cache lookup failed when null (iso-8859-1) is passed as anycompatiblemultirange (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #17066: Cache lookup failed when null (iso-8859-1) is passed as anycompatiblemultirange
|
Список | pgsql-bugs |
On Wed, Jul 21, 2021 at 12:54 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Alexander Korotkov <aekorotkov@gmail.com> writes: > > 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. > > They are not redundant, IIRC. I forget the exact mechanism for > reaching them, but it likely has something to do with aggregates > or variadic functions. If checks aren't redundant, there should be cases when they don't pass. It would be nice to identify these cases and add them to the regression tests. I didn't manage to do this yet. > 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). Thank you! I'll review this and come back to you. ------ Regards, Alexander Korotkov
В списке pgsql-bugs по дате отправления: