Hi Tom,
Thank you for your reply.
I checked and found some weird behavior: We have 32K blocksize.
The incorrect blocks started at block 41 and span over 115 blocks (41 to
155), at the exact block boundary of 32K. Then at 156th block, we have both
tuples with correct number of attributes as well as
PG User writes:
> ... Later we found that invalid header is actually valid header for other
> table's data file. So somehow data of one table got inserted into another
> and both tables have different # of attributes. Can this be possible? Any
> hardware issue can cause this?
There are (at least)
