Re: [BUG] Panic due to incorrect missingContrecPtr after promotion

Поиск
Список
Период
Сортировка
От Imseih (AWS), Sami
Тема Re: [BUG] Panic due to incorrect missingContrecPtr after promotion
Дата
Msg-id 7AF889CF-315C-4FB7-88C0-734FE3F01DE9@amazon.com
обсуждение исходный текст
Ответ на Re: [BUG] Panic due to incorrect missingContrecPtr after promotion  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Ответы Re: [BUG] Panic due to incorrect missingContrecPtr after promotion  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
>    Thus, I still don't see what have happened at Imseih's hand, but I can
>    cause PANIC with a bit tricky steps, which I don't think valid.  This
>    is what I wanted to know the exact steps to cause the PANIC.

>    The attached 1 is the PoC of the TAP test (it uses system()..), and
>    the second is a tentative fix for that.  (I don't like the fix, too,
>    though...)

It is been difficult to get a generic repro, but the way we reproduce
Is through our test suite. To give more details, we are running tests
In which we constantly failover and promote standbys. The issue
surfaces after we have gone through a few promotions which occur
every few hours or so ( not really important but to give context ).

I am adding some additional debugging  to see if I can draw a better
picture of what is happening. Will also give aborted_contrec_reset_3.patch 
a go, although I suspect it will not handle the specific case we are deaing with.


Regards,

Sami imseih
Amazon Web Services


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Aleksander Alekseev
Дата:
Сообщение: Re: Make COPY extendable in order to support Parquet and other formats
Следующее
От: Andres Freund
Дата:
Сообщение: Re: WIP Patch: Add a function that returns binary JSONB as a bytea