Alexander Korotkov <aekorotkov@gmail.com> writes:
> I didn't get we can't add opaque field to SubscriptingRefState without
> adding it to SubscriptingRef, which has to support
> copy/compare/outfuncs/readfuncs
Umm ... all depends on what you envision putting in there. There
certainly can be an opaque field in SubscriptingRefState as long
as the subscript-mechanism-specific code is responsible for setting
it up. You just can't pass such a thing through the earlier phases.
regards, tom lane
