Re: BUG #18815: Logical replication worker Segmentation fault
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sergey Belyashov <sergey.belyashov@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org, Tomas Vondra <tomas@vondra.me>
Date: 2025-02-19T07:06:51Z
Lists: pgsql-bugs, pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix uninitialized index information access during apply.
- 12eece5fd54c 18.0 landed
-
Assert that ExecOpenIndices and ExecCloseIndices are not repeated.
- e596e077bbb3 18.0 landed
-
Fix crash in brininsertcleanup during logical replication.
- 9ff68679b50f 18.0 landed
- 788baa9a25ae 17.5 landed
Sergey Belyashov <sergey.belyashov@gmail.com> writes: > The 4th patch is not applicable for the current REL_17_STABLE branch. Yeah, I saw that, didn't work on fixing it yet. It looked like the diffs were mostly about the ExecOpen/CloseIndices calls in apply_handle_tuple_routing, which we already knew are completely bogus. So I'm hopeful that just removing whichever of them are in v17 will do the job --- but it'll require a full re-test to be sure :-( regards, tom lane