> Cool. I think we can report an error instead of reading wal files,
> if the tablespace, database, or relation is invalid. Does there any
> WAL record that has invalid tablespace, database, or relation OID?
The only sort of validity check we could do here is range checking for the underlying data types (which we certainly
could/shouldadd if it’s known to never be valid for the underlying types); non-existence of objects is a no-go, since
thatdepends purely on the WAL range you are looking at and you’d have to, you know, scan it to see if it existed before
markingas invalid. :)
Thanks,
David
