| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Sergey Belyashov <sergey(dot)belyashov(at)gmail(dot)com> |
| Cc: | Tomas Vondra <tomas(at)vondra(dot)me>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18815: Logical replication worker Segmentation fault |
| Date: | 2025-02-17 20:57:30 |
| Message-ID: | 917262.1739825850@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Further to this ... I'd still really like to have a reproducer.
While brininsertcleanup is clearly being less robust than it should
be, I now suspect that there is another bug somewhere further down
the call stack. We're getting to this point via ExecCloseIndices,
and that should be paired with ExecOpenIndices, and that would have
created a fresh IndexInfo. So it looks a lot like some path in a
logrep worker is able to call ExecCloseIndices twice on the same
working data. That would probably lead to a "releasing a lock you
don't own" error if we weren't hitting this crash first.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2025-02-17 22:31:22 | Re: BUG #18594: CASE WHEN ELSE failing to return the expected output when the same colum is used in WHEN and ELSE |
| Previous Message | Jose Fco. Mojada | 2025-02-17 20:16:51 | Re: Possible bug ¿? missing "ucol.h" in postgre installation |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2025-02-17 21:01:42 | Re: AIO v2.3 |
| Previous Message | Sami Imseih | 2025-02-17 20:39:53 | Re: Proposal - Allow extensions to set a Plan Identifier |