Re: BUG #18815: Logical replication worker Segmentation fault

From: Sergey Belyashov <sergey(dot)belyashov(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Tomas Vondra <tomas(at)vondra(dot)me>
Subject: Re: BUG #18815: Logical replication worker Segmentation fault
Date: 2025-02-19 06:55:08
Message-ID: CAOe0RDxj6QCBHzKY_OGoLHykJ7oAYx2SD_dKs8_aeNBk9WTTXA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Hi,

The 4th patch is not applicable for the current REL_17_STABLE branch.
There are a lot of differences from master in the worker.c.

Best regards,
Sergey Belyashov

ср, 19 февр. 2025 г. в 01:24, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>
> I wrote:
> > I don't intend 0003 for back-patch, but the rest of this has to go
> > back as far as the bug can be observed, which I didn't test yet.
>
> Ah: this bug is new in v17, because neither brininsertcleanup nor
> the whole aminsertcleanup infrastructure exist before that.
>
> So that leaves us with a question of whether 0004 should be
> back-patched any further than v17. There's some attraction
> to doing so to keep the branches in sync; but there's already
> quite a lot of cross-branch churn in worker.c, so on the whole
> I'm inclined to just do v17.
>
> regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2025-02-19 07:06:51 Re: BUG #18815: Logical replication worker Segmentation fault
Previous Message Daniel Westermann (DWE) 2025-02-19 06:39:56 Re: BUG #18817: Security Bug Report: Plaintext Password Exposure in Logs

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-02-19 07:06:51 Re: BUG #18815: Logical replication worker Segmentation fault
Previous Message Michael Paquier 2025-02-19 06:53:11 Re: Proposal to CREATE FOREIGN TABLE LIKE