| From: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: data corruption hazard in reorderbuffer.c |
| Date: | 2021-07-15 21:17:32 |
| Message-ID: | 711C5922-BAFA-44D1-98EE-1F0FA442AF67@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Jul 15, 2021, at 1:51 PM, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)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 recently against a 12.3 database. A similar looking bug was reported a couple years earlier in [2], for which Andres pushed the fix e9edc1ba0be21278de8f04a068c2fb3504dc03fc and backpatched as far back as 9.2. Postgres 12.3 was released quite a 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2021-07-15 22:00:05 | Re: speed up verifying UTF-8 |
| Previous Message | Mark Dilger | 2021-07-15 20:51:41 | Re: data corruption hazard in reorderbuffer.c |