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 1tf5Vy-00HJFf-KA
	for pgsql-bugs@arkaria.postgresql.org; Mon, 03 Feb 2025 23:06:03 +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 1tf5Vw-00HEd6-Ug
	for pgsql-bugs@arkaria.postgresql.org; Mon, 03 Feb 2025 23:06:00 +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 1tf5Vw-00HEcd-MN
	for pgsql-bugs@lists.postgresql.org; Mon, 03 Feb 2025 23:06:00 +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 1tf5Vt-0037AP-2U
	for pgsql-bugs@lists.postgresql.org;
	Mon, 03 Feb 2025 23:06:00 +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 513N5uRH536914;
	Mon, 3 Feb 2025 18:05:56 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: a.glushakov86@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18792: Segmentaion Fault error when changing new parameter
 synchronized_standby_slots
In-reply-to: <18792-1d848ad538b1033c@postgresql.org>
References: <18792-1d848ad538b1033c@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 03 Feb 2025 17:03:32 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <536912.1738623956.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 03 Feb 2025 18:05:56 -0500
Message-ID: <536913.1738623956@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/536913.1738623956%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> I found a discussion of the problem, but it seems that it was not solved=
.
> https://www.postgresql.org/message-id/flat/202411281216.sutbxtr6idnn%40a=
lvherre.pgsql

That discussion began on 2024-11-28, and the fix was pushed a few days
later.  It would require time travel for the fix to have been in 17.2
(released 2024-11-21).  Should be in next week's 17.3, though.

			regards, tom lane