From: | Alex Richman <alexrichman(at)onesignal(dot)com> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Segfault while creating logical replication slots on active DB 14.6-1 + 15.1-1 |
Date: | 2022-12-14 22:59:26 |
Message-ID: | CAMnUB3qYfKkJ6fC=MNr9vrt0gq6FEfzAAb1mD7+aNCAv6zRY8Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi,
We've noticed a segfault bug while creating logical replication slots.
We've seen this on 14.6-1 and 15.1-1 (both installed from postgres
apt-archive repos to debian 11 hosts). We're confident that this behaviour
is not present in 14.5-1.
We can only reproduce this if the server is under load (reads/writes from
clients, perhaps also pg_repacks, reindexes etc). If the server is idle
then we cannot reproduce it.
Dmesg logs:
211935.284834] postgres[2297089]: segfault at 10 ip 000055907a33dd97 sp
00007fff6ebef068 error 4 in postgres[559079e4d000+51a000]
Postgres logs:
2022-12-14 22:33:58 UTC 2297089STATEMENT: SELECT
pg_create_logical_replication_slot('replica_b7fa97cc_28', 'pgoutput',
false);
2022-12-14 22:33:58 UTC 778310LOG: server process (PID 2297089) was
terminated by signal 11: Segmentation fault
2022-12-14 22:33:58 UTC 778310DETAIL: Failed process was running: SELECT
pg_create_logical_replication_slot('replica_b7fa97cc_28', 'pgoutput',
false);
2022-12-14 22:33:58 UTC 778310LOG: terminating any other active server
processes
Journal logs:
Dec 14 22:33:58 c7a2da82-x60-postgres-persistence-onesignal kernel:
postgres[2297089]: segfault at 10 ip 000055907a33dd97 sp 00007fff6ebef068
error 4 in postgres[559079e4d000+51a000]
Dec 14 22:33:58 c7a2da82-x60-postgres-persistence-onesignal kernel: Code:
48 83 c4 08 49 89 c0 5b 41 5c 4c 89 c0 41 5d 5d c3 66 90 83 e3 02 75 b8 e9
71 18 b9 ff e9 d3 18 b9 ff 90 48 89 fe 48 8b 7f f8 <48> 8b 47 >
Let me know if you need any more info.
Thanks,
- Alex.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-12-14 23:27:52 | Re: BUG #17720: pg_dump creates a dump with primary key that cannot be restored, when specifying 'using index ...' |
Previous Message | Tom Lane | 2022-12-14 22:47:40 | Re: BUG #17721: A completely unused CTE negatively affect Query Plan |