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 1sKgKt-00Babs-Qu
	for pgsql-hackers@arkaria.postgresql.org; Fri, 21 Jun 2024 15:37:59 +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 1sKgKr-003Wkx-OS
	for pgsql-hackers@arkaria.postgresql.org; Fri, 21 Jun 2024 15:37:58 +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 <bruce@momjian.us>)
	id 1sKgKr-003Wjl-Ed
	for pgsql-hackers@lists.postgresql.org; Fri, 21 Jun 2024 15:37:57 +0000
Received: from momjian.us ([72.94.173.45])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <bruce@momjian.us>)
	id 1sKgKp-002qfy-Dl
	for pgsql-hackers@postgresql.org; Fri, 21 Jun 2024 15:37:57 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us;
	s=2024011501; h=Content-Type:MIME-Version:Message-ID:Subject:To:From:Date:
	Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:Content-Description:
	In-Reply-To:References; bh=/Vt5S4aGFt4rhERtxSky7Oew3E+Amq1eWm1R2mLvTjo=; b=Pb
	wCSiw7Nlg0psNLQcZpMluxfI1Qj+0FASE+aCwb0NwqAT0VJ7e4G940pFMuXYYObBmwbHtTX/JlyPz
	van51V/cxVahYDy4wvg9EZO3mSq4496J9i+iGyRnSl4gxiajVikKyj7hA6MOJ+Z1Jx6YkgCGG0YpD
	6DyOMMUJYwGH5VsuSIhLomNtf+nulpFTZ2QsCz/IJ9AMdfR/0raayPGzwsMa6oH0CoDSlp4EfgyrX
	l0U5VVDR0qOV3vFrWT4uvxw6pvwF6225M6W3qWLJxxCNQgK+6GrhawQXsj40Yh1jAZkQQtMmg0hYk
	Vp1D+aTU4k04EHIi/vEqMRkXgqm1pcDA==;
Received: from bruce by momjian.us with local (Exim 4.96)
	(envelope-from <bruce@momjian.us>)
	id 1sKgKo-005rMP-1K
	for pgsql-hackers@postgresql.org;
	Fri, 21 Jun 2024 11:37:54 -0400
Date: Fri, 21 Jun 2024 11:37:54 -0400
From: Bruce Momjian <bruce@momjian.us>
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: New standby_slot_names GUC in PG 17
Message-ID: <ZnWeUgdHong93fQN@momjian.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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/ZnWeUgdHong93fQN%40momjian.us>
Precedence: bulk

The release notes have this item:

	Allow specification of physical standbys that must be synchronized
	before they are visible to subscribers (Hou Zhijie, Shveta Malik)

	The new server variable is standby_slot_names. 

Is standby_slot_names an accurate name for this GUC?  It seems too
generic.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.