Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1tkQrz-003stW-UQ
	for pgsql-bugs@arkaria.postgresql.org; Tue, 18 Feb 2025 16:54:51 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-bugs-owner+archive@lists.postgresql.org>)
	id 1tkQrx-00CGQD-Vp
	for pgsql-bugs@arkaria.postgresql.org; Tue, 18 Feb 2025 16:54:49 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1tkQrx-00CGPC-NQ
	for pgsql-bugs@lists.postgresql.org; Tue, 18 Feb 2025 16:54:49 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1tkQrv-001YMU-28
	for pgsql-bugs@lists.postgresql.org;
	Tue, 18 Feb 2025 16:54:48 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 51IGsjaj1249037;
	Tue, 18 Feb 2025 11:54:45 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sergey Belyashov <sergey.belyashov@gmail.com>
cc: Tomas Vondra <tomas@vondra.me>, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18815: Logical replication worker Segmentation fault
In-reply-to: 
 <CAOe0RDwUeZduRUcD1N=BcAk5z3ANPpdyZtr4qNjiY6fPQu=sDw@mail.gmail.com>
References: <18815-2a0407cc7f40b327@postgresql.org>
 <832225.1739810351@sss.pgh.pa.us>
 <CAOe0RDwbowSGv8qeuqyHzJndtwV5JyPEG4YwmaAvgquC=gjz+Q@mail.gmail.com>
 <906545.1739821437@sss.pgh.pa.us> <911898.1739823180@sss.pgh.pa.us>
 <917262.1739825850@sss.pgh.pa.us> <1072645.1739835476@sss.pgh.pa.us>
 <CAOe0RDwUeZduRUcD1N=BcAk5z3ANPpdyZtr4qNjiY6fPQu=sDw@mail.gmail.com>
Comments: In-reply-to Sergey Belyashov <sergey.belyashov@gmail.com>
	message dated "Tue, 18 Feb 2025 09:56:56 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1249035.1739897685.1@sss.pgh.pa.us>
Date: Tue, 18 Feb 2025 11:54:45 -0500
Message-ID: <1249036.1739897685@sss.pgh.pa.us>
List-Id: <pgsql-bugs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-bugs@lists.postgresql.org>
List-Owner: <mailto:pgsql-bugs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-bugs>
Archived-At: 
 <https://www.postgresql.org/message-id/1249036.1739897685%40sss.pgh.pa.us>
Precedence: bulk

Sergey Belyashov <sergey.belyashov@gmail.com> writes:
> Do I need to apply this patch for debugging purposes?

I think we've debugged enough to understand what's happening.
Thanks for the report!

If you just want to get some work done, applying that patch
should be enough to prevent the crash, although I want to
change some other things too.

			regards, tom lane