Re: BUG #16226: background worker "logical replication worker" (PID) was terminated by signal 11: Segmentation
От | Peter Eisentraut |
---|---|
Тема | Re: BUG #16226: background worker "logical replication worker" (PID |
Дата | |
Msg-id | 99b10848-7a3b-f60a-3790-2731ec23f3c9@2ndquadrant.com обсуждение исходный текст |
Ответ на |
BUG #16226: background worker "logical replication worker" (PID |
Ответы |
Re: BUG #16226: background worker "logical replication worker" (PID |
Список | pgsql-bugs |
On 2020-01-22 08:43, PG Bug reporting form wrote: > We have 2 PostgreSQL servers with logical replication between Postgres 11.6 > (Primary) and 12.1 (Logical). Some times ago, we changed column type in a 2 > big tables from integer to text: > , this of course led to a full rewrite both tables. We repated this > operation on both servers. And after that we started to get error like > "background worker "logical replication worker" (PID <pid>) was terminated > by signal 11: Segmentation fault" and server goes to recovery mode. This > error repated several times every 10-15 minutes. When we connected to > logical replication worker process using gdb, we recieved the following > message: > > Program received signal SIGSEGV, Segmentation fault. Could you narrow it down to a reproducible test case? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-bugs по дате отправления: