On Mon, Oct 26, 2026 at 11:35 PM Tom Lane <[email protected]> wrote:
> Jeevan Chalke <[email protected]> writes: > > When validating a PL/pgSQL function with polymorphic arguments or result > > type, > > we substitute a plausible concrete type for each polymorphic type. This > is > > done in two places, cfunc_resolve_polymorphic_argtypes() in funccache.c > for > > arguments and plpgsql_compile_callback() in pl_comp.c for the result > type. > > Both handle anycompatiblerange and anymultirange, but neither handles > > anycompatiblemultirange. This appears to have been missed when > multiranges > > were added in 6df7a9698bb (v14), which added the anymultirange case to > both > > places but did not add any PL/pgSQL test for anycompatiblemultirange. > > Good catch, fix pushed. I didn't bother with the test cases though, > as they seem too specific to help us catch any future problems. > OK. Got it. Thanks for the commit, Tom. > > regards, tom lane > -- *Jeevan Chalke* *Senior Principal Engineer, Engineering Manager* *Product Development* enterprisedb.com <https://www.enterprisedb.com>
