Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gvZco-0006Wq-SV for pgsql-bugs@arkaria.postgresql.org; Mon, 18 Feb 2019 03:29:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gvZcn-0000CA-Cj for pgsql-bugs@arkaria.postgresql.org; Mon, 18 Feb 2019 03:29:45 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gvZcn-0000C2-23 for pgsql-bugs@lists.postgresql.org; Mon, 18 Feb 2019 03:29:45 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gvZcg-0001J6-CT for pgsql-bugs@lists.postgresql.org; Mon, 18 Feb 2019 03:29:43 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id A28172206D; Sun, 17 Feb 2019 22:29:37 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sun, 17 Feb 2019 22:29:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=ZCYt4mUjVN7R4RdduftcgPeHz8j THRSGr2tsk0lrb0w=; b=f+rxYH0bEgVzNWT3fjWsqKb95xJxZe1nhpbaPMI+OvR fE1YSWw0zfVUFUZ6V2Kcgg+iRwbSHlmtQH++mziCURKChXPIppn9w3bRWJItVVYC mW/xg3ArluoXlsJmIXsWpxatz0z2yZyIFQMApdmoMWxOARvfmPy8vORtfkJ7FS6a OnLMW+59q4NpG0v92WqGqqwTCbVgIxmQfnHApbPdobP2yYozPhJJ+YkDLX14eO13 m49VT1gDXMvqtMFn/3ClyySzwcFXZSbylJ6p1ZWGRaLx9Yn7QT6yoREGe8OBg84B pORzjGPI0loMbX2/VxIAE8UvEHxsXW9anV3arRf/OSQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=ZCYt4m UjVN7R4RdduftcgPeHz8jTHRSGr2tsk0lrb0w=; b=ZzgET+qiMgQE5iW0KIBwXg llmgjzMjExygl7m5+beNxWcgduRZqy4pk1dWjqx07QSDEP5zGTizJrxwqH/yACi8 eu5PU0vU6zhTY7Dnrve7Wqxm/d953KTouONNV/nAI4f9wpibeKqDPwF5TVuPNAuf hENihoKe8dJscStST5fk+sNuySZS6fN9WSqizWgwIk9d4rotkV/uM2QkKKFcdDOi jF/3RegK+s7+MP5gr3AD8LYXmoUTuKP/Wu2IaiuIbXOhm9bSdqDR7Ik6NlJR1hQh U8jZUgtyYxgdyZDzUSMq1TfHcd6C33IJyGREc0+dwaW+aqBH8gQ2iSzy67bgDCJw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrudduvddgieegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfquhhtnecuuegrihhlohhuthemucef tddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfghrlhcuvffnffculdejtd dmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgt hhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqne cukfhppeduudekrddvgedurddvgeelrddvgeeknecurfgrrhgrmhepmhgrihhlfhhrohhm pehmihgthhgrvghlsehprghquhhivghrrdighiiinecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from paquier.xyz (mp76f1f9f8.ap.nuro.jp [118.241.249.248]) by mail.messagingengine.com (Postfix) with ESMTPA id C645C10319; Sun, 17 Feb 2019 22:29:33 -0500 (EST) Date: Mon, 18 Feb 2019 12:28:43 +0900 From: Michael Paquier To: Thomas Munro Cc: John Klann , PostgreSQL mailing lists Subject: Re: BUG #15636: PostgreSQL 11.1 pg_basebackup backup to a CIFS destination throws fsync error at end of backup Message-ID: <20190218032843.GD15532@paquier.xyz> References: <20190218025511.GA15532@paquier.xyz> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="IDYEmSnFhs3mNXr+" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --IDYEmSnFhs3mNXr+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Feb 18, 2019 at 04:10:58PM +1300, Thomas Munro wrote: > Well the theory is that it's OK because it's only for directories (the > same case in which case we already tolerate EBADF (for an OS that > nobody documented so we don't really know if/when we can take it > out)). But I agree with you that the patch does not spark joy. If I would vote for this patch, that would be -0.1, meaning that I am not strongly opposed to it, but I don't see any strong point either to do something about it as there are downsides. When in doubt about a back-patch, I use as basic rule to never back-patch so as we are sure that users avoid any surprises and keep relying on the existing design. -- Michael --IDYEmSnFhs3mNXr+ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlxqJmsACgkQnvQgOdby QH3iQA//fL/3wJp/G4EebCpLejJmW9pUyVjOEql65eV47VOCLvvHaLeBGXSODOVt TDuQLCH7KZPeEC4UiG2cOvCUpb8AmZRP47gfuPVpSMJGO8c+6dikMWDdhSWRlorM BGjjjM87Bz8FBFCbGpw8zYKqBG76XWyFHIXka+x+qsQNf5pIJavwE8nJvFAdL1Xv nrzImaXgowmPP8iPRH3Yv9dDFqYQjuuqrSK/zCjG1DRmvNVPIhUlJ6b8qYdinssc n4ceD6XU5D+PBgQ6M0viuXYGs/s38SSlNrECfW51YZvKM/AxPou1C5e71O6a0vDN 7jJysr8+B993/7uuaBVE1qSDTimLU2KCA9OSOAFkqIQxMIGAO9Nwc5pzKiR0vC35 DWAQEiyxQ94HyZMz+90AfsAJGDdJbHTBVT/F/bd0XVB80pNXlEtJjw/TElPBQfIw nqERiJzUDNwkhwv60MVKsKQfKWz5dBsbdKwj3sfvNE4hsvkIi5Xjr06PbstLH/ib yMj8xKZWrLZ2Pd0ow0DI+duZ8/H5gUDp/cTAopLhLitqNgYuGi94h5Qqi5MMRFVq gYdo7n1SaJcjuDT+VOiCLmWKgkZUuAUAWEBnQBxahroakXLZwvNaSgholZa5g4L3 5ii4fJb0vyPw04tHJZa/a3kvUN29Wimqp2tiSFY3nnh0IpwKXO0= =GO1d -----END PGP SIGNATURE----- --IDYEmSnFhs3mNXr+--