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 1lMvqw-0002pK-8a for pgsql-hackers@arkaria.postgresql.org; Thu, 18 Mar 2021 16:50:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lMvqv-0002mc-4L for pgsql-hackers@arkaria.postgresql.org; Thu, 18 Mar 2021 16:50:29 +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 1lMvqu-0002mV-UB for pgsql-hackers@lists.postgresql.org; Thu, 18 Mar 2021 16:50:28 +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 1lMvqs-0001Wc-Qf for pgsql-hackers@postgresql.org; Thu, 18 Mar 2021 16:50:28 +0000 Received: from hnk.local (p2350207-ipbf2126funabasi.chiba.ocn.ne.jp [114.167.184.207]) by oss.nttdata.com (Postfix) with ESMTPSA id 93F38623C6; Fri, 19 Mar 2021 01:50:22 +0900 (JST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.102.3 at oss.nttdata.com Subject: Re: fdatasync performance problem with large number of DB files To: Bruce Momjian , Thomas Munro Cc: Paul Guo , Tom Lane , Michael Brown , pgsql-hackers References: <823DAB20-5A5E-4F7B-BF8C-D61FA574DEEA@vmware.com> <76de0e61-a553-6003-aeec-cb35ada791cf@oss.nttdata.com> <52453bfc-40fb-7771-05ee-cbd04b6b9b6e@oss.nttdata.com> <4CB921E5-772B-42F9-B14D-D310E709E8F2@vmware.com> <20210318135411.GB8529@momjian.us> <20210318140352.GC8529@momjian.us> From: Fujii Masao Message-ID: <3d1086bd-0881-e0a3-9f4f-bda608f07fdb@oss.nttdata.com> Date: Fri, 19 Mar 2021 01:50:22 +0900 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <20210318140352.GC8529@momjian.us> 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: Archived-At: Precedence: bulk On 2021/03/18 23:03, Bruce Momjian wrote: >> Are we sure we want to use the word "crash" here? I don't remember >> seeing it used anywhere else in our user interface. We have GUC restart_after_crash. > I guess it is >> "crash recovery". > > Maybe call it "recovery_sync_method" +1. This name sounds good to me. Or recovery_init_sync_method, because that sync happens in the initial phase of recovery. Another idea from different angle is data_directory_sync_method. If we adopt this, we can easily extend this feature for other use cases (other than sync at the beginning of recovery) without changing the name. I'm not sure if such cases actually exist, though. Regards, -- Fujii Masao Advanced Computing Technology Center Research and Development Headquarters NTT DATA CORPORATION