On Wed, Jan 22, 2020 at 10:22:55AM +0100, Peter Eisentraut wrote:
> On 2020-01-22 08:43, PG Bug reporting form wrote:
>> , 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?
I suspect that this is the same problem as this report:
https://www.postgresql.org/message-id/16129-a0c0f48e71741e5f@postgresql.org
And it has been fixed here, after 12.1, the fix being available with
12.2:
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=a2aa224e
--
Michael