Re: [BUG] Panic due to incorrect missingContrecPtr after promotion
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: "Imseih (AWS), Sami" <simseih@amazon.com>,
Michael Paquier <michael@paquier.xyz>, Alvaro Herrera <alvherre@alvh.no-ip.org>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2022-08-29T16:54:08Z
Lists: pgsql-hackers
On Wed, Aug 10, 2022 at 4:37 AM Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote: > So, it seems that the *standby* received the inconsistent WAL stream > (aborted-contrecord not followed by a overwriting-missing-contrecord) > from the primary. Thus the inconsistency happened on the primary, not > on the standby. > > So... I'm still failing to draw the big picutre of what is happening > here. For the benefit of anyone who may be looking at this thread in the archive later, I believe this commit will have fixed this issue: -- Robert Haas EDB: http://www.enterprisedb.com
Commits
-
Prevent WAL corruption after a standby promotion.
- 0b3ff539dd34 10.23 landed
- 002fba80ebde 11.18 landed
- 3c0ef0832748 12.13 landed
- 3f2701cda590 13.9 landed
- 0e54a5e27494 14.6 landed
- eb29fa38895c 15.0 landed
- 6672d7913929 16.0 landed
-
Fix "missing continuation record" after standby promotion
- caaeb88ff7ae 14.3 landed
- c714ebd0e8c1 12.11 landed
- 9d92582abf91 15.0 landed
- 9ade3c09a5d1 10.21 landed
- 98eb3e06ce3a 13.7 landed
- 199cd7b59a16 11.16 landed