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 1qxcpy-002Im2-9d for pgsql-hackers@arkaria.postgresql.org; Tue, 31 Oct 2023 00:42:30 +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 1qxcpw-00HKkD-TM for pgsql-hackers@arkaria.postgresql.org; Tue, 31 Oct 2023 00:42:28 +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 1qxcpw-00HKin-JU for pgsql-hackers@lists.postgresql.org; Tue, 31 Oct 2023 00:42:28 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qxcpu-003uL5-Dy for pgsql-hackers@lists.postgresql.org; Tue, 31 Oct 2023 00:42:28 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 52DDC5C020C; Mon, 30 Oct 2023 20:42:25 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 30 Oct 2023 20:42:25 -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=1698712945; x=1698799345; bh=BM naohSoVLgmk3tlg4AzZfMUbxJM9hSTrkh2KE0NwDM=; b=h+mIH31EfQS2PaNFsg KsDQchQUC/FYC+GJJBMzOAklF7bh3OoZd9ytQfHHFje7sZY5Td0fvMEWyQSHgXEu jbp4G12SX+isKzghADuyKnttV5/KaT4VcPOqb8FU7kA4DzGq9djB+HatZFFaLvNs FNCTJnGiKuJURIejYqmOJJnopqtO/WW4lMMrqofsPoXMnJC66DAA/VZGWt4XRXjK by3OpKp2xMIUjwy6+2krI6baooxf/UE5kE+6hnoXqQdWo8kQGHVx3qi0fyCAbd34 HfqW/5Hp4thM7QxgeKOq39KSVQYUE7iLCyJEJLx46vO++ucQv6VJ+CdYn5IRRk4C mUSQ== 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=1698712945; x=1698799345; bh=BMnaohSoVLgmk 3tlg4AzZfMUbxJM9hSTrkh2KE0NwDM=; b=InNKiZqu+4IksT+lm+2AUTBJrXm7c JUt9VEeCahqw9VRW8nYH/f1lrkZKokUXXhlJJrpcqjxQX7/aj7SEcNwdSBA14Nsj ufgpFMaZ2SZnEHWsI+G1OgXpBVTDukBn1HtvNtU1U8+lXf0xfF/9HtpqMj4x8Vz3 hZXVwRMWCpkuBvCOQThsUR5UCAQUnblIlvXGzO/wVCkCd2uZ3w4OOZZZolmNG7l+ V1GG99/IQs6PZfkcobu3Aac9QgRx9FzJImmXZO768DDDgZHaoe9DSheOD9NONqkK cjjb/6ve28l2oR7RCDFXP/Xt2sOQ2/TH4oOHBKkhOK2DCjn8HyVOVRGdQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedruddtuddgvdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdljedtmdenucfjughrpeffhffvvefukfhfgggtuggjsehgtderredt tddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesph grqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepteelieefudffhffhtdetleeg geegfffhkeeuveetiefgudduvedutefggeeivdejnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiih ii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 30 Oct 2023 20:42:21 -0400 (EDT) Date: Tue, 31 Oct 2023 09:42:18 +0900 From: Michael Paquier To: Roberto Mello 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> <0f25d737-64c8-4ef3-9873-f2d4f44b1431@pgmasters.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="AF7qVRWbZAn1dsxe" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --AF7qVRWbZAn1dsxe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Oct 30, 2023 at 10:32:28AM -0600, Roberto Mello wrote: > I realize the original use of "touch" is a valid shortcut for what I > suggest above, however that will be less clear for the not-so-un*x-inclined > users of Postgres, while for some it'll be downright confusing, IMHO. It > also provides the advantage of being crystal clear on what needs to be done > to fix the problem. Indeed, "touch" may be better in this path if we'd throw an ERROR to enforce a given policy, and that's more consistent with the rest of the area. -- Michael --AF7qVRWbZAn1dsxe Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmVATWoACgkQnvQgOdby QH0Ffw/9Fd3I5s5AJfCcgelPrlqrf0/+8pLfh9JC3idOdDyob6s6JgG6ogj3tiGL 0QTWo6naFR2U0xPzOViyfd8BU9rmfJQ6gMq1Z3IKB+wKJCkFsWLHlgWVpBieQQBM 2oYEqtq456xtZWAPStRHGljmbUFhKY8oHoQrXdPqeL4rBttaAP0h43aechIeuLUW oy95dve3gncW4MdikRVbpKNewvv6Xvb+HuldvZtcd9ZDTSVi2LpNiQj3X+uRkTHq enC3TfXLRo7X0dNVmycfZswMBSSGm9UavzWrgVT2nxFwcih6yDWc4H/87OqVFHeg uovAOcFlNdlm6Z8pkizKQL1BK0/MPB/tIW5wb26qMBq59/1ZF0Zdw0uG54F1YJt4 uTWAJpZ3wJW3CblvWQyNKdNTiO1GrJvd1wiUkb/ASpLzNZjtn+zT/BHWhIt4gre/ EOH9pUyH9F7vpqh8Q7JUFCtzrkfS/0NuzVkZkZTvKlkhdo3jHDxPUw5fxi+Tvq/g HFebDD8LSVq5MbTx6fSQ4FZ40O+NGmnIYSLWyw5MBuOLpucPCCgPpE0f3tGAsJTB tgwU4HFbsjhLmL0MsEgsUzMVJvsra2CJO9/YEDVYmJbrnBLYb8HbtDURC/kTy9Yj VPXL9g1saPvs7NoXkG3kQyicEdN7bOFLyTNepTGMqdIS9jHrxZk= =Z6aS -----END PGP SIGNATURE----- --AF7qVRWbZAn1dsxe--