Re: Segmentation Fault in logical decoding get/peek API
От | Andres Freund |
---|---|
Тема | Re: Segmentation Fault in logical decoding get/peek API |
Дата | |
Msg-id | 20180220175530.6ib4b3ngzkipekgs@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Segmentation Fault in logical decoding get/peek API (Sudalai <sudalait2@gmail.com>) |
Ответы |
Re: Segmentation Fault in logical decoding get/peek API
|
Список | pgsql-bugs |
Hi, On 2018-02-19 05:20:14 -0700, Sudalai wrote: > PostgreSQL backend crashing with segmentation fault 11, while consuming big > transaction changes using pg_logical_slot_(peek|get)_changes. We are using > postgresql version 9.5.10. Just to be sure, could you check that 9.5.11 shows the same problem? > About the big transaction : pg_xlog_dump shows 161426 records, and it spread > across 3 WAL files. > > BackTace of the backend : > > Program received signal SIGSEGV, Segmentation fault. > ReorderBufferCommit (rb=0xd17dc8, xid=<value optimized out>, > commit_lsn=7224098593984, end_lsn=<value optimized out>, commit_time=<value > optimized out>, origin_id=<value optimized out>, origin_lsn=0) at > /home/test/compile/../postgresql-9.5.10/src/backend/replication/logical/reorderbuffer.c:1380 > 1380 change->action = REORDER_BUFFER_CHANGE_INSERT; > > #0 ReorderBufferCommit (rb=0xd17dc8, xid=<value optimized out>, > commit_lsn=7224098593984, end_lsn=<value optimized out>, commit_time=<value > optimized out>, origin_id=<value optimized out>, origin_lsn=0) at > /home/test/compile/../postgresql-9.5.10/src/backend/replication/logical/reorderbuffer.c:1380 Unfortunately this does not seems to provide enough information to debug the problem. Could you develop a reproducer we can run locally? - Andres
В списке pgsql-bugs по дате отправления: