>> ... And implementing it would require introducing weird
>> corner cases into the tuple toaster, because it might now come across
>> TOAST pointers that point to a no-longer-existent table, and have to
>> consider that to be a no-op instead of an error condition.
> we will compile a patch within the next days to cover this case.
I'm not sure which part of "no" you didn't understand, but: I do not
believe this is worth making the toast code less robust for.
regards, tom lane