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 1tiaeX-0007iB-Sk
	for pgsql-bugs@arkaria.postgresql.org; Thu, 13 Feb 2025 14:57:21 +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 1tiaeV-009AJA-QP
	for pgsql-bugs@arkaria.postgresql.org; Thu, 13 Feb 2025 14:57:20 +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 1tiaeV-009AGx-HE
	for pgsql-bugs@lists.postgresql.org; Thu, 13 Feb 2025 14:57:20 +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 1tiaeT-000d9r-2F
	for pgsql-bugs@lists.postgresql.org;
	Thu, 13 Feb 2025 14:57:19 +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 51DEvEGC3587299;
	Thu, 13 Feb 2025 09:57:15 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: weijie1006jl@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18810: invalid value for parameter
 "synchronized_standby_slots" Caused error:"Segmentation fault"
In-reply-to: <18810-226c754a49ea511f@postgresql.org>
References: <18810-226c754a49ea511f@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Thu, 13 Feb 2025 10:43:54 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <3587297.1739458634.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Thu, 13 Feb 2025 09:57:14 -0500
Message-ID: <3587298.1739458634@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/3587298.1739458634%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> log detail:
> 2025-02-13 11:45:28.563 CST    [4015389]LOG:  00000: received SIGHUP,
> reloading configuration files
> 2025-02-13 11:45:28.563 CST    [4015389]LOCATION: 
> process_pm_reload_request, postmaster.c:2104
> 2025-02-13 11:45:28.564 CST    [4015389]LOG:  22023: invalid value for
> parameter "synchronized_standby_slots": "slave"
> 2025-02-13 11:45:28.564 CST    [4015389]DETAIL:  replication slot "slave"
> does not exist
> 2025-02-13 11:45:28.564 CST    [4015389]LOCATION:  call_string_check_hook,
> guc.c:6927
> 2025-02-13 11:45:28.564 CST    [4015389]LOG:  F0000: configuration file
> "/data/pgdata/pg5433/data/postgresql.conf" contains errors; unaffected
> changes were applied
> 2025-02-13 11:45:28.564 CST    [4015389]LOCATION: 
> ProcessConfigFileInternal, guc.c:616
> 2025-02-13 11:45:28.687 CST    [4015389]LOG:  00000: system logger process
> (PID 1511029) was terminated by signal 11: Segmentation fault

I believe this is one of the bugs fixed in the just-released 17.3:

    <listitem>
<!--
Author: Álvaro Herrera <alvherre@alvh.no-ip.org>
Branch: master [3c5f9f12c] 2024-12-03 17:50:57 +0100
Branch: REL_17_STABLE [9abdc1841] 2024-12-03 17:50:57 +0100
-->
     <para>
      Avoid crash when a background process tries to check a new value
      of <varname>synchronized_standby_slots</varname> (Álvaro Herrera)
      <ulink url="&commit_baseurl;9abdc1841">&sect;</ulink>
     </para>
    </listitem>

			regards, tom lane