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 1iSFkv-0003ds-0I for pgsql-committers@arkaria.postgresql.org; Wed, 06 Nov 2019 07:29:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iSFkt-0002Se-ES for pgsql-committers@arkaria.postgresql.org; Wed, 06 Nov 2019 07:29:27 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iSFkt-0002SX-7S for pgsql-committers@lists.postgresql.org; Wed, 06 Nov 2019 07:29:27 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iSFkp-0001aU-V4 for pgsql-committers@lists.postgresql.org; Wed, 06 Nov 2019 07:29:26 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id 5EB6E521; Wed, 6 Nov 2019 02:29:20 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 06 Nov 2019 02:29:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=fxpx5lovh0/zB61T5AipE7Wjz9e0jhj7mFhRiLME/ zA=; b=OAHsrvehDLXbZhDtImZxjtyGrjvqxbeYSh4KGJXCWwHM7WX8xtsvETBqf mPjevHh2ZWqQhPNpXp+AZdJ947EkxXTzJyRth/SS804m4aSiVPEjkcw4Ok0r12t4 ECEQmLdY82ABlJhI5kjggmX3jC68xKO3Kr/VNiz4s87CkyrR5Z7knw9XunF1l76y uW7Jx3Lnzq1gHZRT+SKB2db7e7VbaavVYupHHJVCOlKuxQ9j5kiwVO6eOVeM3KBj x8leaIZ+gJQT+pDSp4NIayh6YZoWctOUmPYS4Gyd/+3Tv3K+Elq4FSiHqkPWISC2 Na8xEAMQI8SQDj29MCdVoqQKkkZxA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudduiedguddtkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefuvfhfhfhokffffgggjggtgfesthejredttdefjeenucfhrhhomheprfgv thgvrhcugfhishgvnhhtrhgruhhtuceophgvthgvrhdrvghishgvnhhtrhgruhhtsedvnh guqhhurggurhgrnhhtrdgtohhmqeenucffohhmrghinhepvdhnughquhgrughrrghnthdr tghomhenucfkphepleefrddvgedvrddugeejrdejleenucfrrghrrghmpehmrghilhhfrh homhepphgvthgvrhdrvghishgvnhhtrhgruhhtsedvnhguqhhurggurhgrnhhtrdgtohhm necuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from april.pezone.net (p5df2934f.dip0.t-ipconnect.de [93.242.147.79]) by mail.messagingengine.com (Postfix) with ESMTPA id ED31680060; Wed, 6 Nov 2019 02:29:18 -0500 (EST) Subject: Re: pgsql: doc: Further clarify how recovery target parameters are applied To: Fujii Masao , Alvaro Herrera References: <20191105132123.GA1578@alvherre.pgsql> Cc: pgsql-committers@lists.postgresql.org From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Wed, 6 Nov 2019 08:29:17 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2019-11-06 05:48, Fujii Masao wrote: > Patch attached. As I argued upthread, IMO it's better to remove > the latter description from the doc and the patch does that. > Also the patch adds "mainly" into the former description. I think we should list explicitly what is applied and what is not. This is the reference documentation after all. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services