On Tue, May 12, 2020 at 3:36 AM Robert Haas <robertmh...@gmail.com> wrote:
> On Sun, May 10, 2020 at 11:21 PM Andy Fan <zhihui.fan1...@gmail.com> > wrote: > > Looks this doesn't mean a crash. If the test case(subscription/t/ > 013_partition.pl) > > failed, test framework kill some process, which leads the above > message. So you can > > ignore this issue now. Thanks > > I think there might be a real issue here someplace, though, because I > couldn't get a core dump last week when I did have a crash happening > locally. I forget to say the failure happens on my modified version, I guess this is what happened in my case (subscription/t/013_partition.pl ). 1. It need to read data from slave, however it get ERROR, elog(ERROR, ..) rather crash. 2. The test framework knows the case failed, so it kill the primary in some way. 3. The primary raises the error below. 2020-05-11 09:37:40.778 CST [69541] sub_viaroot WARNING: terminating connection because of crash of another server process 2020-05-11 09:37:40.778 CST [69541] sub_viaroot 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. Finally I get the root cause by looking into the error log in slave. After I fix my bug, the issue gone. Best Regards Andy Fan
