| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | vadim(at)postgrespro(dot)co(dot)il, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16226: background worker "logical replication worker" (PID <pid>) was terminated by signal 11: Segmentation |
| Date: | 2020-01-22 09:22:55 |
| Message-ID: | 99b10848-7a3b-f60a-3790-2731ec23f3c9@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Drawater | 2020-01-22 12:26:11 | 12.1 Partitioned Table Creation Bug |
| Previous Message | PG Bug reporting form | 2020-01-22 07:43:23 | BUG #16226: background worker "logical replication worker" (PID <pid>) was terminated by signal 11: Segmentation |