Vinod Sridharan <vsridh90@gmail.com> writes:
> -- create textops operator class without triconsistent
OK, got it, and I concur that we need to make shimTriConsistentFn()
restore the state of the entryRes array before it returns. But
I don't understand why you're concerned about "However, this would
also reset it during the regular triConsistent check per tuple"?
I think the point is basically that this function is violating
the expectation that triconsistent functions not change the state
of that array. That expectation doesn't depend on what the call
site is.
regards, tom lane