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 ) id 1qsWuR-008O3u-ET for pgsql-hackers@arkaria.postgresql.org; Mon, 16 Oct 2023 23:22:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qsWuP-0050MO-ED for pgsql-hackers@arkaria.postgresql.org; Mon, 16 Oct 2023 23:22:02 +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 ) id 1qsWuN-0050MF-LX for pgsql-hackers@lists.postgresql.org; Mon, 16 Oct 2023 23:22:01 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qsWuD-0014zH-0C for pgsql-hackers@lists.postgresql.org; Mon, 16 Oct 2023 23:21:58 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id AC2535C035A; Mon, 16 Oct 2023 19:21:47 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 16 Oct 2023 19:21:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm3; t=1697498507; x=1697584907; bh=GS iyXM66fojpkGX3KDft/DxnPtQRkVPtaOnnjL1EE2s=; b=XIiWNCMOjb6E9BN1+1 bA3B/+2r6ekFnVQ/efWpYebdlrbFIMMR0XhScxRPswPzfavU1qY2x1LxaZo/DiB1 ++q/R9cWCMDWiYy7Nvaz2veZ+SFHm9OUTsILyXost+GTrcEpKU7sIEzUE58FBrz0 voBhLIBgiHysWv+6qVEyKKC2VhGsXYAFj8ds2NA7aJdRJIzUP13GsuTzYZhtG2qE LXkyqtiPO9UdrDk5eI7jKPxhBwc/5fqZoDWNabBCsAhNwyVHiWcKydj7pWu8LJzq cECXpFTPp+XvERtWXKjVtqRjx0k4Bq1iS1OYGlMY+9IY2YIGDX3mnFsI4XE1Boae lF2g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1697498507; x=1697584907; bh=GSiyXM66fojpk GX3KDft/DxnPtQRkVPtaOnnjL1EE2s=; b=oDHwnmAyXgZ1kcaWwUW7hSk9Dk8fH 8ARcnHY5Jun/OyLNfrpqxUuiQzX1W3W/rOyaOAdrkaFwjV+F/1KqNLG+evMQhhLA oxYCcDcoprfyMdPwycOofDFLBckgZcTXyj59aEuhulhJdpIiyfGjFKHZrbpkNHbL iKdVOz22cTvSfJkJSTm/vxojZ1lm1+BiBHgjzNLIy2JDUwIs5hg63z8FuoYf6V+a HYYgz+Xjr2Gc/SNrRp4MrJ+zoaH+2VR+IFIz+H4f29WNZ6SxPzfEKzB7MDk4eCNQ UAH/3oxVIAasLrVpDk0TgT93VpBPxWTXbMDRGgYo4t9QkhyZKAFreEGNA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrjedugddvtdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfg hrlhcuvffnffculdefhedmnecujfgurhepfffhvfevuffkfhggtggujgesghdtreertddt vdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprg hquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpeegffejvefgveduvdejtddvtdei jeehudeuledvudeftdfgfeejvdekveekiedvvdenucffohhmrghinhepphhoshhtghhrvg hsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhf rhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 16 Oct 2023 19:21:44 -0400 (EDT) Date: Tue, 17 Oct 2023 08:21:39 +0900 From: Michael Paquier To: Laurenz Albe Cc: David Steele , Kyotaro Horiguchi , pgsql-hackers@lists.postgresql.org, zxwsbg12138@gmail.com, david.zhang@highgo.ca Subject: Re: Requiring recovery.signal or standby.signal when recovering with a backup_label Message-ID: References: <20230928.125851.2051261991058034791.horikyota.ntt@gmail.com> <4f94351c-24e2-cf32-82d3-1e1bf89a0f5e@pgmasters.net> <58a6e18b112b4cd8bd9ab66d3f0ff5e77ada8799.camel@cybertec.at> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="tT7qug/pVlpHEI1V" Content-Disposition: inline In-Reply-To: <58a6e18b112b4cd8bd9ab66d3f0ff5e77ada8799.camel@cybertec.at> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --tT7qug/pVlpHEI1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Oct 16, 2023 at 05:48:43PM +0200, Laurenz Albe wrote: > I don't have strong feelings either way. If you have backup_label > but no signal file, starting PostgreSQL may succeed (if the WAL > with the checkpoint happens to be in pg_wal) or it may fail with > an error message. There is no danger of causing damage unless you > remove backup_label, right? A bit more happens currently if you have a backup_label with no signal files, unfortunately, because this causes some startup states to not be initialized. See around here: https://www.postgresql.org/message-id/Y/Q/17rpYS7YGbIt@paquier.xyz https://www.postgresql.org/message-id/Y/v0c+3W89NBT/if@paquier.xyz > I cannot think of a use case where you use such a configuration on > purpose, and the current error message is more crypric than a plain > "you must have a signal file to start from a backup", so perhaps > your patch is a good idea. I hope so. -- Michael --tT7qug/pVlpHEI1V Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmUtxYMACgkQnvQgOdby QH0GJBAAqkiXWN/8ruzXHZk7qtTVfD+iMloQ39f3/vR+HWRh1rFAf0E/SmmapgqB r5RgtKjPlKjBnwqXQ7ZqLDn0owGx3cPjjOl+y7JzpUHZ05nze5bE9bEgKB6rblol ft8VVInG7pv2PF2YrMNifQtncj6HeWEII2jjM3Ojne01RO7Vv9yQ5TB/5myvFzt9 nq3n227NBDsGTCOs6Z9z1aFYgbfdn4Q2nGuv07Bj9LfbOtoFyGtpMPSmlDCxXN5q 05yaQduIuUPBYeLkdUIOyQ5G2Jykm8m+2Kf+FqMJGVGS5+pB3/768FCKhLyCsRMa qlrIA30fcNXV5hkFUMYgqPtjRolJIddFuX8K4ECbOeVRCGX7+3lQjbeeIohyJdbB GicZSnIQzcnqcvPXZRgDWJ/tQNtf8f1RXHCaNWOwJxa17k/N+WJ+HhBe2FcFPZ3C yBieSRbnPaw1GMmfIhe97k0k2qLBuMJwSVT4KKzk7mi+z/yPBRKJzmfnarQxoI9A 1tGseeuvUPKjzfmOSHIKZH/jeMfCQGwOHcLW86EWnKZfixI7IsNhpS/l7PMfPXlR sMbJZMtj3SZ/ZoYgxzZ16/RUS1FqM3hUN+E9mhW+QFcZpN3NHldZcP29y9LQ2BCP m/U24I1AvAuico4zPI8wlE7EEB5ZpMfurWUxai40y78nxYXeC6g= =0dzV -----END PGP SIGNATURE----- --tT7qug/pVlpHEI1V--