Re: Segmentation Fault in logical decoding get/peek API

Поиск
Список
Период
Сортировка
От Jeremy Finzel
Тема Re: Segmentation Fault in logical decoding get/peek API
Дата
Msg-id CAMa1XUiAGtcmbAWJNXutbfeJUNSF+X9jYhuNjxev3PDhUDbvUw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Segmentation Fault in logical decoding get/peek API  (Andres Freund <andres@anarazel.de>)
Ответы Re: Segmentation Fault in logical decoding get/peek API  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-bugs
Дерево обсуждения
Yes, please do. And if that fails, is is realistic to test without those
additional extensions?  If not, where's their source?

So yes, I just reproduced the same assert abort on 10.7, so issue is still there.

I still need pg_fact_loader, but I was able to strip out any custom C code from the test and I am still able to produce the crash.  I dropped extensions pgl_ddl_deploy and pglogical_ticker.  pg_fact_loader can optionally use a pg background worker, but I am bypassing that and thus only running plpgsql functions, and still producing the crash.  This makes me doubt that it could have anything to do with these extensions.

If interested, here is the source for them:

I want to see if I can reproduce the crash on a fresh cluster.  Is there anything else you want me to try at this point?

Thanks,
Jeremy

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

Предыдущее
От: PG Bug reporting form
Дата:
Сообщение: BUG #15642: UPDATE statements that change a partition key and FDW partitions problem.
Следующее
От: Julien Rouhaud
Дата:
Сообщение: Re: BUG #15572: Misleading message reported by "Drop functionoperation" on DB with functions having same name