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 1in186-0003DC-Lo for pgsql-bugs@arkaria.postgresql.org; Thu, 02 Jan 2020 14:07:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1in183-0001a9-RJ for pgsql-bugs@arkaria.postgresql.org; Thu, 02 Jan 2020 14:07:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1in183-0001a2-If for pgsql-bugs@lists.postgresql.org; Thu, 02 Jan 2020 14:07:11 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1in180-0000by-RU for pgsql-bugs@lists.postgresql.org; Thu, 02 Jan 2020 14:07:10 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 40E6C21FDF; Thu, 2 Jan 2020 09:07:07 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 02 Jan 2020 09:07:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=AP2qbFc5zljCJE43HhACJZVjv2S 9TsA3/Ge4s9zHXlo=; b=d0WJP11rqwcic3+XNDqIp5OdKz55id2iq3Vdzh/iIg+ AM8XNO4soZq4y7vKXpgzCYXasCrbWoU2p8FIqHRyPHVhD1nG83h89uANFY5oiLDs mD3qmG7YliucL/CTiztbzX/dbFiTMlX33GvhCIdoXuQeyaccAk1mL4JgOnj78ErH fQH+Zm7W+4c5+1tMPRtIM5y8VopxEOCDzdc3kTuoPc5zgPMbc/ORA4RPtyodUv5a ZDTrrSgelqTF+0zDc4fJ2UOx3sUoF1NDBUWZqxN3EDmFnj3a46xzPKfBcdfaPhSY N+duzg5SWSH55JBzkDBKHVmBv37Pc/9nkUUSUfups3Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=fm1; bh=AP2qbF c5zljCJE43HhACJZVjv2S9TsA3/Ge4s9zHXlo=; b=AY+OcSaXH4kQsQDs31BvZd w9fEvxrYPU+tTmXX5vMhxMg/gzZd20BrEUa1jDaJnREqJKXNvJP4QoE8xwT7TV5w CJTIaMoYq7dQI3D16qch+PhvrmklfDnbnL6CZLj/1Hs9Mcw7PBeIStck2Q4+9+Bj tyMi8zHlQk00obnTTXHKjyQIQmJSOUaJtcNnV465X36aGQMmd+wDloDk3I0bqWS5 dgiVW4Of3vXS4bG1I/vLV1DA0/5iqP+TPCwEkeciTT1RAWUs3OQ0a2AH5mRywzhl 26pdXw4OzkWUj4Ee05rkunXCccTnRM0MmpyB0cGSf5fcSyUWDywYxq0orp6C17Zw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrvdeguddgieduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgfrhhlucfvnfffucdljedtmdenucfjughrpeffhf fvuffkfhggtggujgesghdtreertddtvdenucfhrhhomhepofhitghhrggvlhcurfgrqhhu ihgvrhcuoehmihgthhgrvghlsehprghquhhivghrrdighiiiqeenucfkphepudduuddrud dtvddrudektddrudekheenucfrrghrrghmpehmrghilhhfrhhomhepmhhitghhrggvlhes phgrqhhuihgvrhdrgiihiienucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from paquier.xyz (ee0822lan1.rev.em-net.ne.jp [111.102.180.185]) by mail.messagingengine.com (Postfix) with ESMTPA id 1D7A430607B4; Thu, 2 Jan 2020 09:07:05 -0500 (EST) Date: Thu, 2 Jan 2020 23:07:03 +0900 From: Michael Paquier To: johanfo@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16182: Error in logs from "renaming temporary statistics" Message-ID: <20200102140703.GA4841@paquier.xyz> References: <16182-06f613c9fd10f3bf@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="qMm9M+Fa2AknHoGS" Content-Disposition: inline In-Reply-To: <16182-06f613c9fd10f3bf@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jan 02, 2020 at 06:55:37AM +0000, PG Bug reporting form wrote: > I have checked the permissions of the folder and files, and I can not see > why this occurs. This error would occur on Windows when a concurrent process, external to Postgres, has a file opened in non-shared mode while Postgres tries to work on it. In this case the work is done by pgrename() on Postgres side which is a custom wrapper in src/port/dirmod.c to handle this kind of scenarios with a retry-and-sleep logic, but it gives up after 10s (100 tries of 100ms each). This issue could be usually caused by an antivirus or something that scans the files of the disk where Postgres data is located. In this case, the best thing you could do is to prevent the concurrent activity from happening by filtering out Postgres data folder. Nobody can guess why this file is held opened that long though without looking at your server when the problem happens. -- Michael --qMm9M+Fa2AknHoGS Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl4N+QcACgkQnvQgOdby QH37aA/+MdVeJ5aBg0KfC+XxPwXMECOOcSdHjAgQIEE5/vC+xpjGc5LHfumdLAVZ 0dgZY1BLVRuDE2y+gC0QM23UzqSYAkiNPa7wO8HCBZKyWEsxwDiuF3SkgpfDBqOA OAOwNgUofV1Ss+K+6koPDw9vfRDg9/gadynsLtnve/zSmHncpWNu5hUsTNyrB1/6 MDT+ijWlNM3MIUE2qYk9z42jOih/u0cS0mwXqERuSGe+6Sl0b1FYDwN90qTF9Nsf T2bZL6iar1wkEHqkcnui8FZwR1o9knHZ3U114nwMNP4mFXb6j6OzTO/2UpU1pqI7 KQS4MpP0uc9s1sRoDuRGu3ed9LAb6dkwGjrw34ZCAHveJdoA2c8nm/xMiAjvfMT5 ISrx94SQRrtKV1ejmbCQnMDErc5o0O+1J7FlUzhtnNrjHzJI3MEeGiWOnZEXX0Nw NqQZ6LHsts3dwbJ4aO5Z7EFhyuogPEYtY1X8L2cZsKeWwQttfSJLNVXpjBrqqes+ ALzE6DS3aIo/hgWnwHxKoqKeykEJWTk2BBuLpLga9R9QzC6ECT7B7puK3zJa7MyC FrA3MCO9J5zDC+Z3/8lpyhqumxbyQrFldZrKYxUfuaWPmkB76Scp33OkwLkVQKyj hIEVyYsRM0JpkChLTXErjCT2bsPg9fqCcqN4xVAw/dZShkBMoP4= =rVcH -----END PGP SIGNATURE----- --qMm9M+Fa2AknHoGS--