Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lEs9J-000597-VF for pgsql-docs@arkaria.postgresql.org; Wed, 24 Feb 2021 11:16:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lEs9I-0004fU-TD for pgsql-docs@arkaria.postgresql.org; Wed, 24 Feb 2021 11:16:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lEs9I-0004fN-Nd for pgsql-docs@lists.postgresql.org; Wed, 24 Feb 2021 11:16:08 +0000 Received: from oss.nttdata.com ([49.212.34.109]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lEs9F-0006wY-7t for pgsql-docs@lists.postgresql.org; Wed, 24 Feb 2021 11:16:08 +0000 Received: from hnk.local (p2710230-ipbf1703funabasi.chiba.ocn.ne.jp [123.216.93.230]) by oss.nttdata.com (Postfix) with ESMTPSA id 14552626F4; Wed, 24 Feb 2021 20:16:00 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.102.3 at oss.nttdata.com Subject: Re: incoorect restore_command To: Michael Paquier , Philipp Gramzow Cc: pgsql-docs@lists.postgresql.org References: <161397938841.15451.13129264141285167267@wrigleys.postgresql.org> <478b5b00-5ab3-a1b5-65f4-19b4409c720b@philphonic.de> From: Fujii Masao Message-ID: <3c8a08bb-3eaa-cdc6-08f9-3298342722c2@oss.nttdata.com> Date: Wed, 24 Feb 2021 20:15:59 +0900 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; 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 2021/02/24 16:52, Michael Paquier wrote: > On Wed, Feb 24, 2021 at 07:24:17AM +0100, Philipp Gramzow wrote: >> I agree, using a proper extension would be more straightforward. I'm sure >> that's the reason why someone changed our archive_command. > > Okay, let's do so in the docs then. Others may have comments to > offer, so I'll first wait a bit before applying my suggestion from > upthread. I agree with this change. But I have one question; why do those commands use different archive directories? Isn't it better to use the same one? Regards, -- Fujii Masao Advanced Computing Technology Center Research and Development Headquarters NTT DATA CORPORATION