| From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | START_REPLICATION SLOT causing a crash in an assert build |
| Date: | 2022-09-06 23:40:49 |
| Message-ID: | YxfagaTXUNa9ggLb@ahch-to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
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.
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.
--
Jaime Casanova
Director de Servicios Profesionales
SystemGuards - Consultores de PostgreSQL
| Attachment | Content-Type | Size |
|---|---|---|
| gdb_start_replication_slot_crash.txt | text/plain | 6.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Reid Thompson | 2022-09-07 00:17:25 | Re: Add the ability to limit the amount of memory that can be allocated to backends. |
| Previous Message | Jeff Davis | 2022-09-06 23:26:12 | Re: pg_auth_members.grantor is bunk |