Hello,
When currently trying to lock a virtual tuple the returned error
will be a misleading `could not read block 0`. This patch adds a
check for the tuple table slot being virtual to produce a clearer
error.
This can be triggered by extensions returning virtual tuples.
While this is of course an error in those extensions the resulting
error is very misleading.
--
Regards, Sven Klemm
