Michael Paquier wrote: > So the problem appears when an expression needs to use > COERCION_PATH_ARRAYCOERCE for a type coercion from one type to another, > which requires an execution state to be able to build the list of > elements. The clause matching happens at planning state, so while there > are surely cases where this could be improved depending on the > expression type, I propose to just discard all clauses which do not > match OpExpr and ArrayExpr for now, as per the attached. It would be > definitely a good practice to have a default code path returning > PARTCLAUSE_UNSUPPORTED where the element list cannot be built. > > Thoughts?
I found a related crash and I'm investigating it further. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
