Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gqrWH-0004cI-35 for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Feb 2019 03:35:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gqrWF-0000BR-Di for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Feb 2019 03:35:31 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gqrWD-00009o-Lj for pgsql-hackers@lists.postgresql.org; Tue, 05 Feb 2019 03:35:31 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gqrW6-0000Di-78 for pgsql-hackers@postgresql.org; Tue, 05 Feb 2019 03:35:28 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id E63E521BAD; Mon, 4 Feb 2019 22:35:20 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Mon, 04 Feb 2019 22:35:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=pXv6uGRCjt+8Hg5r03X8u9bhmad M97BweSzys9Pj88w=; b=GOkw1OtweMu3xkowFo2PS/ZTxel3nlNPQq4gB2agadR v5xPV6QjHTlle1uh/ddnygxQCyOBMO1/WUNGqoXPt2fzvC0bJ24l4yRCGA62DElB RgEVH4775izh7Kht+kD9Whav6k1r1VWxNmHGt7JbMlBO0ATVhiiwNYt1/WOen65j wLU4Q4hlj0d7p5T/7w3mWbugIvVx/ho4hNTBa5ZCcE/VIdt74plfXjjFigmB3rAn pea6Y90N//g1Nk6bb7ApRwbvT6sBHchbZ+7XS9sHAKGzw5p1MUobScdv9b7pz+sW Wow+UFaSrXK0mcpVgAmfed2oP3qb+uV9sA92QSTV7AA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=pXv6uG RCjt+8Hg5r03X8u9bhmadM97BweSzys9Pj88w=; b=G192aw6JN1X0mHZEdZudW+ 0zQepWtQ28y9HQghX8XIiXWEDmvX3Hl7UlzAGKTo1KCrs+n30grLI25WcMi0cIiy c/8p1xaflAbhMLpDMxWSO7ugueLAi0Wv6pVcu8idL7jMHzwUdRi9I3a7ytVKEfYY jOX1Vakn55OQh8uF23Bjvmh2tFU497lLNzsUUyzkGoOj5Nx16VoRn5oDX5IWudHK Zv3fTqkCAgLhgU/kzlvjysT0QIgvoEhv3atCX6XBL2hGO4s9Ymivz9UknMbdDUbT gk1vnXKtApmwMkw9BxZrk5cCjU+s7yT0CVFR1zGN4pMFFT/Zl30jiocoa8Pfj0rg == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrkeehgdeivdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnegfrhhlucfvnfffucdljedtmd enucfjughrpeffhffvuffkfhggtggujgesghdtreertddtvdenucfhrhhomhepofhitghh rggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprghquhhivghrrdighiiiqeenuc fkphepiedurddvudehrddufeejrdduiedvnecurfgrrhgrmhepmhgrihhlfhhrohhmpehm ihgthhgrvghlsehprghquhhivghrrdighiiinecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from paquier.xyz (c137162.net61215.cablenet.ne.jp [61.215.137.162]) by mail.messagingengine.com (Postfix) with ESMTPA id 6C296E412C; Mon, 4 Feb 2019 22:35:18 -0500 (EST) Date: Tue, 5 Feb 2019 12:35:14 +0900 From: Michael Paquier To: Peter Eisentraut Cc: pgsql-hackers Subject: Re: Allow some recovery parameters to be changed with reload Message-ID: <20190205033514.GC1882@paquier.xyz> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Izn7cH1Com+I3R9J" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --Izn7cH1Com+I3R9J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 04, 2019 at 11:58:28AM +0100, Peter Eisentraut wrote: > I think the recovery parameters >=20 > archive_cleanup_command Only triggered by the checkpointer. > promote_trigger_file > recovery_end_command > recovery_min_apply_delay Only looked at by the startup process. > can be changed from PGC_POSTMASTER to PGC_SIGHUP without any further > complications (unlike for example primary_conninfo, which is being > discussed elsewhere). I agree that this subset is straight-forward and safe to switch. The documentation changes look right. -- Michael --Izn7cH1Com+I3R9J Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlxZBHIACgkQnvQgOdby QH2hkg//bD4ne9Kt19SIAE5xVxF8fUzbO/cG/fp7iFO8HfoGBi+WB7wKdpaReGd4 k6iHrmHTf1LbloJtIEwzDjKAvoVQsIoTu5KNqi/EhOOcWT/j8KLhWvQpI7X2k8K/ vZACKN9dxl6mGcydCFB+hD1p9aM05QRr8pEWfUnntg9V9vv33Kc8DOQwqSbeuZtn lmTiPx2BKqyyFmWXLY4D8e18EVbzolN9IB2aRpZtff6DGswotylQHbyFd5BdQCMO pL2NaFZGOt16wcCPV8SF6oK0M2T72Xx3UbueZUA6G7vxRUEPfrABfpQ1v259tfZx s28bzIS0jCyiRpLhhb5TEfKPyAFtyRO9LE/Mjlw3xmZ96mGYujMj0P/mCV5hmkHd oSImko7K0P7pyu0TOvgjvLdbsE6zaJLubvlwI+O/M+ubc8HyLDYsBq1LpDUSMWjR aiLKnNehkC/6a0H8YbGE7JHR1k/WYPG7QjVki3u++fwIR7sUWc5aXJ0Q4jAhsvQJ qjIbyfBAOEMhtCgOsCFhLROMPAmdpAS/29hMl/Op3erTM+tDno6k+2m3AEQXQqDr YCyr3TcdUu4+R1uuabjZJnE7SlgD4aIAPBJB80Q3zkhzExjIjppWSkGArfL6/bDt 1sD+9HpNX6vVTHT2IdKLEOV5zunrjrFhqNd1VjDmbgNHZkyNVfo= =ZQ/P -----END PGP SIGNATURE----- --Izn7cH1Com+I3R9J--