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 1qj2YS-00935d-Rv for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Sep 2023 19:08:08 +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 1qj2YR-002HsT-Dt for pgsql-hackers@arkaria.postgresql.org; Wed, 20 Sep 2023 19:08:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qj2YR-002HsA-0y for pgsql-hackers@lists.postgresql.org; Wed, 20 Sep 2023 19:08:07 +0000 Received: from mail-oi1-x22a.google.com ([2607:f8b0:4864:20::22a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qj2YN-006N21-Li for pgsql-hackers@postgresql.org; Wed, 20 Sep 2023 19:08:06 +0000 Received: by mail-oi1-x22a.google.com with SMTP id 5614622812f47-3ab2a0391c0so113221b6e.1 for ; Wed, 20 Sep 2023 12:08:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695236882; x=1695841682; darn=postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=4FPcFVE/470atEI3zg3DrvmjdURVwUZFmoWCbWfxvts=; b=BXvnsYjYXo0LkLx3/cWdyrJEN2MuFUaLsmKZg/lzRX6c1aqr8uZ6beICEvwl7P2yVQ gcBcJl/cWJO74vlLo+ZggHjxa/dRvR7qAtbyvDNkbi2xASWZQ1I+AQqJwvB3RauEXSvv Blu7cIeT7/Zs5rapQLdJNjLBhjH/k93Jvp/qldTTO5PgqhhmXPvqI91tGX7San+/YSTN 4L+TJwkGko8Jiyw30dBLpO0JwO9ftho9ZH9Kh+GLIVDISvsnfxJXHL9tUsN/GW2fi2rV zAFuIpBZ9EX3oxO5tmf3A2NZkpRmRGxDH920wzGQxjeXGFgzZhfi1xK/iXTJN4M80RZn iJpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695236882; x=1695841682; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=4FPcFVE/470atEI3zg3DrvmjdURVwUZFmoWCbWfxvts=; b=Ph0E6Xez5phXO7QvgXDnM8yWE1KL/H1vXEmaQ1VqIFNKejzx0TPL/mB98bq8RPCMTt QIwp+vBT8T0jtRRlq2d0bEME7Yk6EqNvVf9C/1XeM3D4uMSayRBGL44KU0Nlo4iAYYms 9aVRceMJzzPpnQ82aRkDu9HySUAZ1Y+HXwoZ5wqwQvzaDbopnTYdUu1a+tO2pbeVVahT GRl3DYjxPynjhoRezlSkq9LRNe7SS375jNJPJw+BMTdYua4tYmckRPJikqgJSGL66UBt s4Sqb9Td3B8F5FB4gnjIo2MtZAC8/lk6H5eFUiyqnJCjgKNjlxIw5G1uXtzMhQBJBUmX 5BHA== X-Gm-Message-State: AOJu0Yxfy7zCfZ3SHKtawtT9WWZL5SC6f4LSgckFMRytrJ09iU80dq5Z YnH8Rn+uYTEjnU3enlKiZ+8= X-Google-Smtp-Source: AGHT+IGKgKuZ5bxfgj76zvbXHOw/H+3AU7otJmYsruk/MeCeh2AgWfLV5nMfoLBuGnjqtRSLthyLFg== X-Received: by 2002:a05:6808:2010:b0:3a4:316c:8eeb with SMTP id q16-20020a056808201000b003a4316c8eebmr4006792oiw.40.1695236881961; Wed, 20 Sep 2023 12:08:01 -0700 (PDT) Received: from nathanxps13 ([2600:1700:48f8:340f:c587:3a48:c1bf:c35]) by smtp.gmail.com with ESMTPSA id j15-20020a056808034f00b003a8560a9d34sm6122309oie.25.2023.09.20.12.08.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Sep 2023 12:08:01 -0700 (PDT) Date: Wed, 20 Sep 2023 12:07:48 -0700 From: Nathan Bossart To: Maxim Orlov Cc: Justin Pryzby , Michael Paquier , Thomas Munro , David Steele , Fujii Masao , Bruce Momjian , Paul Guo , Tom Lane , Michael Brown , pgsql-hackers@postgresql.org Subject: Re: should frontend tools use syncfs() ? Message-ID: <20230920190748.GA2960472@nathanxps13> References: <20220413115412.GM26620@telsasoft.com> <20230729214010.GA189456@nathanxps13> <20230901180851.GC3180181@nathanxps13> <20230901183100.GD3180181@nathanxps13> <20230906000853.GA105086@nathanxps13> <20230906232908.GA537242@nathanxps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Sep 20, 2023 at 03:12:56PM +0300, Maxim Orlov wrote: > As a solution, I suggest renaming sync_method in xlog module to > wal_sync_method. In fact, > appropriate GUC for this variable, called "wal_sync_method" and I see no > reason not to use > the exact same name for a variable in xlog module. +1 I think we should also consider renaming things like SYNC_METHOD_FSYNC to WAL_SYNC_METHOD_FSYNC, and sync_method_options to wal_sync_method_options. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com