BUG #16205: background worker "logical replication worker" (PID 25218) was terminated by signal 11: Segmentation

Поиск
Список
Период
Сортировка
От PG Bug reporting form
Тема BUG #16205: background worker "logical replication worker" (PID 25218) was terminated by signal 11: Segmentation
Дата
Msg-id 16205-5f93551b36ff4f34@postgresql.org
обсуждение исходный текст
Ответы Re: BUG #16205: background worker "logical replication worker" (PID25218) was terminated by signal 11: Segmentation  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-bugs
The following bug has been logged on the website:

Bug reference:      16205
Logged by:          Firdaus Firdaus
Email address:      pendekar.senja@outlook.com
PostgreSQL version: 12.1
Operating system:   Ubuntu 16.04.6 LTS
Description:

Hi there,
I got error when replicate with native logical method from PostgreSQL 11.6
to PostgreSQL 12.1, I will connecting table partition to table partition
from Version 11.6 to Version 12.1, but after all tables already replicated
around more than 2 hours, server can't access and recovery mode. please help
to advice, below log.
2020-01-15 08:31:40 WIB [24943] LOG:  background worker "logical replication
worker" (PID 25218) was terminated by signal 11: Segmentation fault
2020-01-15 08:31:40 WIB [24943] LOG:  terminating any other active server
processes
2020-01-15 08:31:40 WIB [25214] WARNING:  terminating connection because of
crash of another server process
2020-01-15 08:31:40 WIB [25214] DETAIL:  The postmaster has commanded this
server process to roll back the current transaction and exit, because
another server process exited abnormally and possibly corrupted shared
memory.
2020-01-15 08:31:40 WIB [25214] HINT:  In a moment you should be able to
reconnect to the database and repeat your command.
2020-01-15 08:31:40 WIB [24943] LOG:  all server processes terminated;
reinitializing
2020-01-15 08:31:41 WIB [25222] LOG:  database system was interrupted; last
known up at 2020-01-15 08:31:40 WIB
2020-01-15 08:31:41 WIB [24943] LOG:  received fast shutdown request
2020-01-15 08:31:41 WIB [25222] LOG:  recovered replication state of node 1
to 2EA/B70B8DC8
2020-01-15 08:31:41 WIB [25222] LOG:  database system was not properly shut
down; automatic recovery in progress
2020-01-15 08:31:41 WIB [25222] LOG:  invalid record length at 132/DF032918:
wanted 24, got 0
2020-01-15 08:31:41 WIB [25222] LOG:  redo is not required
2020-01-15 08:31:41 WIB [25222] LOG:  checkpoint starting: end-of-recovery
immediate
2020-01-15 08:31:41 WIB [25222] LOG:  checkpoint complete: wrote 0 buffers
(0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.051 s,
sync=0.000 s, total=0.062 s; sync files=0, longest=0.000 s, average=0.000 s;
distance=0 kB, estimate=0 kB
2020-01-15 08:31:41 WIB [24943] LOG:  abnormal database system shutdown
2020-01-15 08:31:41 WIB [24943] LOG:  database system is shut down


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

Предыдущее
От: "David G. Johnston"
Дата:
Сообщение: Re: libpq parameter parsing problem
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: libpq parameter parsing problem