Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qYEGz-0016Xa-Tj for pgsql-hackers@arkaria.postgresql.org; Mon, 21 Aug 2023 23:25:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qYEGy-00Btt0-Fz for pgsql-hackers@arkaria.postgresql.org; Mon, 21 Aug 2023 23:25:24 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qYEGy-00Btss-5k for pgsql-hackers@lists.postgresql.org; Mon, 21 Aug 2023 23:25:23 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qYEGu-000Ebm-Gk for pgsql-hackers@postgresql.org; Mon, 21 Aug 2023 23:25:22 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 854D6320092D; Mon, 21 Aug 2023 19:25:18 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 21 Aug 2023 19:25:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm1; t=1692660318; x=1692746718; bh=fh MlmpMPL2Vaz09Qg/DiPMW7a8+mwnW4hjzVHyxIu/I=; b=Z7cxWyEbV0hzd9LgTp uZlpuh0pSWEI1ObYHV49E7k1RqNxQp10jWGY0A7jTALqqg6USRp9J5V+GMGJz5/C NI3x93f7y7xuGCrDkifprnwfQOOsx5bz085+MUfmTzazf1PREqaf/i7sGNje/s/w Cxg5Y7Hsl94wlMSO5wQKex1MGSHtr+CecxTgZPYbZkPQGhsJHFWiBqwLCUaE63J6 zgpQas5YbufvIU0KJn9UFStgRrxMD0OPc7zJa6Wsf+BfO/D6nPBp21vKBfN0diEC Ro+PXqUGxlcVfVYQ4DWAR73QPZMgk4Cd+gOYJRjlP/5uy9tKSDGhv/Kp34fkvd2+ cBhA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1692660318; x=1692746718; bh=fhMlmpMPL2Vaz 09Qg/DiPMW7a8+mwnW4hjzVHyxIu/I=; b=QtHKVUZ21IiiJInjz9NnqW1Tm+A/5 akou2vomKljJL2MioABuItrpn7NYHqMl8qfln6IDzwqyTaMZZWG+/t/Cl1PcnPhr 65k3tNe08SZ9bacA2zGYYr9kuMi+eby9wf0ESTYKb3PiKsyhcyiqmnFIc8rOkZvO fioIjN0qRgHfV5TjgcKerRRNRmNyMvUz8TX3OyyHm9jpcvEloDY5A56mk0K+pQol wZ3wxUrnj6+vaXlA0jHGMVyMQ+Y94dIlFdQVKfkLyEkESw5nlJROtzhvBKtYAfcj sZP1EWknLtJT2q2OFRcV/ddAiEmYq/+BnhXMlQO/aATpEAUDBKNaZ08JQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedruddvtddgvdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdljedtmdenucfjughrpeffhffvvefukfhfgggtuggjsehgtderredt tddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesph grqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepteelieefudffhffhtdetleeg geegfffhkeeuveetiefgudduvedutefggeeivdejnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiih ii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 21 Aug 2023 19:25:13 -0400 (EDT) Date: Tue, 22 Aug 2023 08:25:11 +0900 From: Michael Paquier To: Robert Haas Cc: Nathan Bossart , Justin Pryzby , Thomas Munro , David Steele , Fujii Masao , Bruce Momjian , Tom Lane , Michael Brown , pgsql-hackers@postgresql.org Subject: Re: should frontend tools use syncfs() ? Message-ID: References: <20220413115412.GM26620@telsasoft.com> <20230729214010.GA189456@nathanxps13> <20230731175138.GA432880@nathanxps13> <20230731183946.GB537853@nathanxps13> <20230801163707.GA862840@nathanxps13> <20230808200606.GA1384393@nathanxps13> <20230816151705.GB2651383@nathanxps13> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="K9/SCQJUc8U/8USl" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --K9/SCQJUc8U/8USl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Aug 21, 2023 at 04:08:46PM -0400, Robert Haas wrote: > Doesn't seem worth it to me. I think --no-sync is more intuitive than > --sync-method=none, it's certainly shorter, and it's a pretty > important setting because we use it when running the regression tests. No arguments against that ;) -- Michael --K9/SCQJUc8U/8USl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmTj8lcACgkQnvQgOdby QH0RMRAApCNqpwECAT0mfSyFPnJXpSZpD9E2jnu92gpBD+E8KsyWuUTkDi9FTz89 CvxhT9X6vmede7DyjuRyqXRQb3lNvS+Ekito0gSpW21DS/GJC/5i24CRdVWHIdF9 BZc1z+T6s6czjpEHLepwP8pDe5IGgaK5LRDmc/7iSVe7jZMKXgh5Mu92FXIKGwIB wR78olycJ1XPEXiCp8Cj/YL3NgtQkgy4DJ5DvjKVA7WD4xHW5fiWGHIW81+dGASG ctOZBft/7tFcz27oWyxeK69hVGULNIxay7a4iztrYKtaw12NYlbtbCKATwTQEbgc 2/M3mtBkWH1WPgYrw430WkTFBeICoo0WVdIZ1SJ4Kaf07VLOsaO2JvNoJZXmiVH8 s/hsLl4bh+gZ4i9NbCK3N0MX6o21kzRynu5pEjpjYDxyEEznH1J/7pqqfURpshtX gKl+q+PMNOF6TaLRHj2IUT/XnigDeSXu6TvjKCiX53HK7csKkTCrbZprMkqjz1Jr +EmLCcaEOYHArEqYw6MkftP9rVRlcbTQV3UfT2Qco1D9zoVbzyG2MBhIfNp76TxT JQx6EYZJ8j21pJQeQrm15wv8OxM70YJH2j/It4ycyekQNBYHFkhdSybF9gFGJ04o GhJUoQpuAexRQa9etpxeMHSvi4MBFp1iAvrJ8a3ZfPjoODeqzUU= =YdqE -----END PGP SIGNATURE----- --K9/SCQJUc8U/8USl--