> No, it's far from harmless. As soon as that heap TID gets filled with
> an unrelated tuple, you run the risk of indexscans alighting on and
> perhaps modifying the wrong tuple.
>
>
Tom,
In the Function based indexes on those functions, which we are
suspecting to be a volatile one Or in the datatypes, which we suspect to be
broken, can we have additional checks to ensure that to ensure that this
does not happen? I mean, do you think, that would solve the issue?
Thanks,
Gokul.