Re: Assertion failure during walsender exit - Mailing list pgsql-bugs

At Wed, 8 Dec 2021 10:02:15 +0530, vignesh C <vignesh21@gmail.com> wrote in 
> fileName=0x55cc1872435a "pgstat.c",
>     lineNumber=4852) at assert.c:37
> #4  0x000055cc182d72b6 in pgstat_assert_is_up () at pgstat.c:4852
> #5  0x000055cc182d3dd0 in pgstat_send (msg=0x7ffd5df8a420, len=144) at
> pgstat.c:3075
> #6  0x000055cc182d2214 in pgstat_report_replslot_drop
> (slotname=0x7f853c58e998 "sub1") at pgstat.c:1869
> #7  0x000055cc1832dbe3 in ReplicationSlotDropPtr (slot=0x7f853c58e980)
> at slot.c:696
> #8  0x000055cc1832d8fe in ReplicationSlotDropAcquired () at slot.c:585
> #9  0x000055cc1832d59c in ReplicationSlotRelease () at slot.c:482
> #10 0x000055cc183a7be7 in ProcKill (code=0, arg=0) at proc.c:852

Yeah, this issue has been reported several times and, maybe, is under
discussion.

https://www.postgresql.org/message-id/CAD21AoBgSTF8gp1SKojKRu9dqzN4p1Ob6Mh%3DQgVhGfLO1NtUYA%40mail.gmail.com
https://www.postgresql.org/message-id/OS0PR01MB571621B206EEB17D8AB171F094B59%40OS0PR01MB5716.jpnprd01.prod.outlook.com
https://www.postgresql.org/message-id/CA%2BHiwqEpGF%3DROEvVOqvvDF%3Dw9iaMBx0g5zBBhP62ZFE7vW6O8w%40mail.gmail.com
regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center