On Wed, 18 Dec 2024 at 14:02, Tom Lane <t...@sss.pgh.pa.us> wrote: > So I tried adapting my patch to not make a copy of the input slot, > and it didn't work: I was still getting assertion failures about > the slot not being a MinimalTupleSlot as expected. On investigation > it appears your patch did not fully adjust BuildTupleHashTableExt > for variable input-slot type. You need the attached as well.
Do you have a test case in master that triggers a problem here? Your patch adjusts code that existed prior to d96d1d515, so I'm confused as to why your patch is needed now when it wasn't before. If you're only triggering an issue after patching with your setops patch, are your changes maybe using FindTupleHashEntry() with an eqcomp that isn't compatible with the 'slot' parameter you're passing to that function? David
