On Sat, 8 May 2021 at 14:04, David Rowley <dgrowleyml@gmail.com> wrote: > I'm not opposed to adding some new field if that's what it takes. I'd > imagine the new field will be something like negfuncid which will be > InvalidOid unless the hash function is set and useOr == false
Just while this is still swapped into main memory, I've attached a patch that adds a new field to ScalarArrayOpExpr rather than repurposing the existing field.