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 1pGBW4-00060R-6U for pgsql-hackers@arkaria.postgresql.org; Fri, 13 Jan 2023 04:18:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pGBW2-000695-Bh for pgsql-hackers@arkaria.postgresql.org; Fri, 13 Jan 2023 04:18:06 +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 1pGBW1-00068w-W6 for pgsql-hackers@lists.postgresql.org; Fri, 13 Jan 2023 04:18:06 +0000 Received: from mail-qt1-x829.google.com ([2607:f8b0:4864:20::829]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pGBVv-0003vH-CP for pgsql-hackers@lists.postgresql.org; Fri, 13 Jan 2023 04:18:05 +0000 Received: by mail-qt1-x829.google.com with SMTP id e22so5768438qts.1 for ; Thu, 12 Jan 2023 20:17:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=user-agent: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=zHgha6WTKKZ9x3B6aZUZW0tjbuXcJVDJEeMbDxZUUgw=; b=B8LGtn7a/CAbtp5AUFo3JrnPPoLS8LBFT0eDiR4rf+tkEa/VQPAi5dXKrAbZ1VLUPL nlGQ/kHhG2fOp3CXm/MpTdn9dZ70O+CHcQy5zhY8RDYhJ8lN+ynVKeHTF57OU9ev1i1E mcKRjoyz9zi2VDzHDoV8XxWgpltX2RgSJ4/QzrC13rTH3RTNxCcTLGBN/mhDLMRjR5jl FcdnFmRVfZDSlkkp0J4FBL6Y+vzJ5CzGQAUJt09I6Qq+eSZ796nrVN7cIc3eVLDV3dcm nOBDLouA1PkcdHUfvQMTfgwpwvjkKe1VzrELc/wt6Jmc5aZCKl5wgO3cZa5V9L7U18og UJSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=user-agent: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=zHgha6WTKKZ9x3B6aZUZW0tjbuXcJVDJEeMbDxZUUgw=; b=xWNit/xWnUKBsfaVvMJ0ZXDcaam8AFBydcGOVPuemNJuZqR6+fdeBzsNJrtGg+SV26 0W3S9cj0f7bS5bGJ7nfab6V791mRNjTfPpEwo9fVqLNRgT3+86MA7WjfDBCGG/GQ9lZS gdB+xXUf2umQWrT2tsC8MOGTZdTKwohcrgRKuIw6uDn6condFfbwYYcQxalg9R4tZ9ND yS00jrbCR9KiNz4hgYHi5nqOTnviaGwmxMRyOm08jw+jFCEGcRJXQCvrjjzJn0v/YUVV PMx0S18vlgpTEIPruws3XZqvvUxXPaevE1CsyMGLbC9vU7jxj/QzvDrzk3hVcBinhONs qXAg== X-Gm-Message-State: AFqh2kqUQWVqXLG8nW/gtQ6cpNBgYfQasXm15+abTta9DkydqnmdmUeH vSVhOsLp+mWkR72UtV6lRQdn/w== X-Google-Smtp-Source: AMrXdXuatapoHRxWTo0LYqwrHDmQ1MC8ynXJG1fbUKihXAxxHnXuQthb9eOq6/kCfdUkzCCFPRiluw== X-Received: by 2002:ac8:4e87:0:b0:3ac:c2b8:c with SMTP id 7-20020ac84e87000000b003acc2b8000cmr35051454qtp.25.1673583477538; Thu, 12 Jan 2023 20:17:57 -0800 (PST) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id i4-20020a05620a404400b00704a2a40cf2sm12123592qko.38.2023.01.12.20.17.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 12 Jan 2023 20:17:57 -0800 (PST) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id CAF3680104F; Thu, 12 Jan 2023 22:17:55 -0600 (CST) Date: Thu, 12 Jan 2023 22:17:55 -0600 From: Justin Pryzby To: Andres Freund Cc: Thomas Munro , vignesh C , pgsql-hackers@lists.postgresql.org, Andrew Dunstan , Tom Lane Subject: Re: Cygwin cleanup Message-ID: <20230113041755.GV9837@telsasoft.com> References: <20221021034040.GT16921@telsasoft.com> <20221109010437.GK3775@telsasoft.com> <20230103142537.GM1153@telsasoft.com> <20230112043949.GQ9837@telsasoft.com> <20230113024354.3q4aigbf4fyh2igg@awork3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230113024354.3q4aigbf4fyh2igg@awork3.anarazel.de> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Jan 12, 2023 at 06:43:54PM -0800, Andres Freund wrote: > > It looks like logical decoding may be the "most wrong" place that > > wal_sync_method is being used, so maybe my change is reasonable to > > consider, and not just a workaround. > > I don't follow. What does using fsync_fname() vs fsync_fname_ext() have to do > with pg_fsync() using wal_sync_method? fsync_fname() is just a wrapper around > fsync_fname_ext(). Both end up in pg_fsync(). My patch used fsync_fname_ext() which would cause an ERROR rather than a PANIC when failing to fsync the logical decoding pathname. > Are you actually proposing that we don't PANIC after an fsync for the category > of files that you list here, even with data_sync_retry set? Yes, but I'm referring only to my change to SnapBuildSerialize(). The rest of the verbage was me trying to figure out the history/evolution of pg_fsync usage. -- Justin