On Wed, 15 Jan 2020 at 09:32, Pendekar Dikala Senja <
pendekar.senja@outlook.com> wrote:
>
>
> Here are the logs and our configuration.
> Actually we are facing problem when replicating partition table from 11.6 to 12.1, but if there is no partition table the replication works so well.
> As FYI, our server spec is 16 core and 64GB. And we are using this ubuntu
>
> LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
> Distributor ID: Ubuntu
> Description: Ubuntu 16.04.6 LTS
> Release: 16.04
> Codename: xenial
>
> Can you help us to find out the solution and configuration?
> Thanks for your help
>
> ________________________________ From: Michael Paquier
> Sent: Tuesday, January 14, 2020 6:58 PM
> To:
pendekar.senja@outlook.com;
pgsql-bugs@lists.postgresql.org > Subject: Re: BUG #16205: background worker "logical replication worker" (PID 25218) was terminated by signal 11: Segmentation
>
> On Wed, Jan 15, 2020 at 02:00:48AM +0000, PG Bug reporting form wrote:
> > 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.
>
> Could you provide a backtrace? Looking at the recent commit history,
> we had one fix which could be relevant to you after 12.1 was released:
>
https://www.postgresql.org/message-id//16129-a0c0f48e71741e5f@postgresql.org >
> And here is the commit:
>
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=a2aa224e >
> The problem may be different though, so a backtrace would be good to
> check anyway.
> --
> Michael
Hi,
It looks like that server is crashed due to segmentation fault.
Can you provide call stack(stack trace) of Pid 25218.
To get call stack, you should start server with "-c" option.
Ex: ./pg_ctl -D data -l logfile -c start
How to get stack trace: After crash, you can see core.PID file in your data directory. Attach core file to gdb and fire "bt" command.
Ex: gdb postgres data/core.25218
bt
--
Thanks and Regards
Mahendra Singh Thalor
EnterpriseDB:
http://www.enterprisedb.com