Re: START_REPLICATION SLOT causing a crash in an assert build
От | Andres Freund |
---|---|
Тема | Re: START_REPLICATION SLOT causing a crash in an assert build |
Дата | |
Msg-id | 20220907193908.prfnxnt6diao2fli@awork3.anarazel.de обсуждение исходный текст |
Ответ на | START_REPLICATION SLOT causing a crash in an assert build (Jaime Casanova <jcasanov@systemguards.com.ec>) |
Ответы |
Re: START_REPLICATION SLOT causing a crash in an assert build
Re: START_REPLICATION SLOT causing a crash in an assert build |
Список | pgsql-hackers |
Hi, On 2022-09-06 18:40:49 -0500, Jaime Casanova wrote: > I'm not sure what is causing this, but I have seen this twice. The > second time without activity after changing the set of tables in a > PUBLICATION. Can you describe the steps to reproduce? Which git commit does this happen on? > gdb says that debug_query_string contains: > > """ > START_REPLICATION SLOT "sub_pgbench" LOGICAL 0/0 (proto_version '3', publication_names '"pub_pgbench"')START_REPLICATIONSLOT "sub_pgbench" LOGICAL 0/0 (proto_version '3', publication_names '"pub_pgbench"') > """ > > attached the backtrace. > > #2 0x00005559bfd4f0ed in ExceptionalCondition ( > conditionName=0x5559bff30e20 "namestrcmp(&statent->slotname, NameStr(slot->data.name)) == 0", errorType=0x5559bff30e0d"FailedAssertion", fileName=0x5559bff30dbb "pgstat_replslot.c", > lineNumber=89) at assert.c:69 what are statent->slotname and slot->data.name? Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: