| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: START_REPLICATION SLOT causing a crash in an assert build |
| Date: | 2022-09-07 19:39:08 |
| Message-ID: | 20220907193908.prfnxnt6diao2fli@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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_REPLICATION SLOT "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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2022-09-07 19:45:54 | Re: proposal: possibility to read dumped table's name from file |
| Previous Message | Justin Pryzby | 2022-09-07 18:43:34 | Re: Add SPLIT PARTITION/MERGE PARTITIONS commands |