pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Fujii Masao <masao.fujii@oss.nttdata.com>
To: Bruce Momjian <bruce@momjian.us>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Paul Guo <guopa@vmware.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Brown <michael.brown@discourse.org>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: fdatasync performance problem with large number of DB files
Date: Fri, 19 Mar 2021 01:50:22 +0900
Message-ID: <3d1086bd-0881-e0a3-9f4f-bda608f07fdb@oss.nttdata.com> (raw)
In-Reply-To: <20210318140352.GC8529@momjian.us>
References: <CA+hUKGLABi5asn5yFXBrAC0d3dGBN8QHvLq=27sa7thCQV4Z1w@mail.gmail.com>
	<CA+hUKGK0hZ1jBCF6r+J9=CVwpAUTU7EB3_SUp5Owp0zym4eksg@mail.gmail.com>
	<823DAB20-5A5E-4F7B-BF8C-D61FA574DEEA@vmware.com>
	<CA+hUKGJi11x6cHJQNeDnLRvk1GMX18DJQaKFqwCOjgeFnbiVKA@mail.gmail.com>
	<76de0e61-a553-6003-aeec-cb35ada791cf@oss.nttdata.com>
	<CA+hUKGJTERHhpAja3KvwF=0qPTgnFB=QPrR=sHmqWKJ2o2mr2Q@mail.gmail.com>
	<52453bfc-40fb-7771-05ee-cbd04b6b9b6e@oss.nttdata.com>
	<4CB921E5-772B-42F9-B14D-D310E709E8F2@vmware.com>
	<CA+hUKGLkoO6i2qoP6u9uKPx8SL4MGzMnT+xQJ+p_x3FggH1Z8A@mail.gmail.com>
	<20210318135411.GB8529@momjian.us>
	<20210318140352.GC8529@momjian.us>



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





view thread (49+ messages)  latest in thread

Message-ID: <3d1086bd-0881-e0a3-9f4f-bda608f07fdb@oss.nttdata.com>
Permalink:  ../3d1086bd-0881-e0a3-9f4f-bda608f07fdb@oss.nttdata.com/
Also on:    postgresql.org/message-id/3d1086bd-0881-e0a3-9f4f-bda608f07fdb@oss.nttdata.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: masao.fujii@oss.nttdata.com, bruce@momjian.us, thomas.munro@gmail.com, guopa@vmware.com, tgl@sss.pgh.pa.us, michael.brown@discourse.org
  Subject: Re: fdatasync performance problem with large number of DB files
  In-Reply-To: <3d1086bd-0881-e0a3-9f4f-bda608f07fdb@oss.nttdata.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox