Re: data corruption hazard in reorderbuffer.c

> On Jul 15, 2021, at 1:51 PM, Mark Dilger <mark.dilger@enterprisedb.com> wrote:
>
> one common error I see

Another common error is of the form

    ERROR:  could not map filenode "base/16384/16413" to relation OID

resulting from a ddl statement having not been written correctly, I think.  This, too, has shown up in [1] fairly
recentlyagainst a 12.3 database.  A similar looking bug was reported a couple years earlier in [2], for which Andres
pushedthe fix e9edc1ba0be21278de8f04a068c2fb3504dc03fc and backpatched as far back as 9.2.  Postgres 12.3 was released
quitea bit more recently than that, so it appears the bug report from [1] occurred despite having the fix from [2]. 

[1] https://www.postgresql-archive.org/BUG-16812-Logical-decoding-error-td6170022.html
[2] https://www.postgresql.org/message-id/flat/20180914021046.oi7dm4ra3ot2g2kt%40alap3.anarazel.de





—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company