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-hackers-owner+archive@lists.postgresql.org>)
	id 1tkeBa-005eve-GF
	for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Feb 2025 07:07:58 +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-hackers-owner+archive@lists.postgresql.org>)
	id 1tkeAa-004uf2-MZ
	for pgsql-hackers@arkaria.postgresql.org; Wed, 19 Feb 2025 07:06:56 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	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 1tkeAa-004uet-DA
	for pgsql-hackers@lists.postgresql.org; Wed, 19 Feb 2025 07:06:56 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by magus.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 1tkeAY-001iPU-1F
	for pgsql-hackers@lists.postgresql.org;
	Wed, 19 Feb 2025 07:06:56 +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 51J76pG81956237;
	Wed, 19 Feb 2025 02:06:51 -0500
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>
Subject: Re: BUG #18815: Logical replication worker Segmentation fault
In-reply-to: 
 <CAOe0RDxj6QCBHzKY_OGoLHykJ7oAYx2SD_dKs8_aeNBk9WTTXA@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>
 <1249036.1739897685@sss.pgh.pa.us> <1761873.1739911114@sss.pgh.pa.us>
 <1773117.1739917446@sss.pgh.pa.us>
 <CAOe0RDxj6QCBHzKY_OGoLHykJ7oAYx2SD_dKs8_aeNBk9WTTXA@mail.gmail.com>
Comments: In-reply-to Sergey Belyashov <sergey.belyashov@gmail.com>
	message dated "Wed, 19 Feb 2025 09:55:08 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1956235.1739948811.1@sss.pgh.pa.us>
Date: Wed, 19 Feb 2025 02:06:51 -0500
Message-ID: <1956236.1739948811@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: 
 <https://www.postgresql.org/message-id/1956236.1739948811%40sss.pgh.pa.us>
Precedence: bulk

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