| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [BUG] Panic due to incorrect missingContrecPtr after promotion |
| Date: | 2022-08-29 16:54:08 |
| Message-ID: | CA+TgmoY+Wgqfj+dLdL_ESaf4YX8hKSDkkfXfZvHrsPPzZ2o_1w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 10, 2022 at 4:37 AM Kyotaro Horiguchi
<horikyota(dot)ntt(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2022-08-29 16:54:39 | Re: [BUG] Panic due to incorrect missingContrecPtr after promotion |
| Previous Message | Robert Haas | 2022-08-29 16:32:30 | Re: standby promotion can create unreadable WAL |