Date: Tue, 16 Mar 2021 10:20:20 +0900
From: Michael Paquier <michael@paquier.xyz>
To: yarik97.6@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16927: Postgres can`t access WAL files
Message-ID: <YFAH1LbeUeXTFcEM@paquier.xyz>
References: <16927-67c570d968c99567@postgresql.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="Il7pC/GPZj/XWd6/"
Content-Disposition: inline
In-Reply-To: <16927-67c570d968c99567@postgresql.org>
Archived-At: 
 <https://www.postgresql.org/message-id/YFAH1LbeUeXTFcEM%40paquier.xyz>
Precedence: bulk


--Il7pC/GPZj/XWd6/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 15, 2021 at 02:19:57PM +0000, PG Bug reporting form wrote:
> Recently, I had updated 4 clusters postgreSQL from version 9.6 to 13.2, a=
nd
> now have issue with errors that you can see below from log file. There is
> high frequency of how this error gets occurred.
> With such type of errors I can`t set up replication slot and I worry about
> is it safe for data in DB cluster.=20
> I already took some actions to get rid of this error: 1) enabled exclusio=
ns
> in GPO for Microsoft Defender (clusters directory and postgres process)=
=20
> 2) checked system with sfc tool.
> 3) checked user & system rights for cluster directory.
> But nothings from this works.
> Here are some lines from log file.
> 2021-03-15 15:44:54.674 EET [3992] LOG:  could not rename file
> "pg_wal/000000010000086E000000C6": No such file or directory
> 2021-03-15 15:48:38.884 EET [3992] LOG:  could not rename file
> "pg_wal/000000010000086D000000E7": Permission denied
> 2021-03-15 15:48:49.813 EET [3992] LOG:  could not rename file
> "pg_wal/000000010000086D000000FD": Permission denied
> 2021-03-15 15:49:00.642 EET [3992] LOG:  could not rename file
> "pg_wal/000000010000086E00000033": Permission denied

There have been multiple reports of this issue for 13, though we have
not been able to determine if this was coming from Postgres or if a
recent Windows update is causing that.  Here, you basically say that
all stable versions of PostgreSQL are seeing this problem, which is
new to me.  Particularly,  9.6.20 did not have any issues but 9.6.21
is showing this problem, right?  Or did you update from an even older
version, say 9.6.19 or 9.6.18?

Are all those instances involved with streaming replication?  What is
exactly the version of your Windows server?  d726e44f catches my
eyes here, looking at the diffs between both versions..
--
Michael

--Il7pC/GPZj/XWd6/
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmBQB9QACgkQnvQgOdby
QH1W9g//Ug5pqZOiT+RklIEIPl+CBqhv7oX3v4ampvHoH6WEoVSUA+u0l4bFNAiu
z3oBlqX/e/RAdowy7sTGdcij3oa2P792LffKUYZlzxkv1KioaLAuFxdBLVaPq2kB
D3q29Gf7pdqcEJ22oJkD8vWmpN27GnDnIwpPYVFQ9E2jQdkwWFjg8qwfN2vCkLW+
SFWeWCDYwye19BXrS69Z49+FJIiwT9U45h+x/Oo5CcR9hqDXNAgBWOx04ocBCHYs
tsPOXvNnXBYIWP6bSGx6Dbjd9V0HCdoKGvYyR/m7RyYmJEDZLMrVEUE/zZ3qBXO3
033PG1Z3NU9Q3x4Ets2Hu8hSXkLZK1XCGNqLqXZq4vc/VFO3y2tk6B+ONoSkU/lj
qCUM6YFBVpxDNfVp1/ZTCXFa4i1+hpT+Q487Dv2l7ZbkXfIovHk5U8nZegD9V1no
88kX4fElZatF+6aMfpYhOFbDusdhXm7099XcIpV2/zDLiIElTo7BmrFOkdUDxwGk
Ybc1GfFmynsH+78+4LKxEcnj7XYqwkcL/pOaMzLL8qHalfaEMu9q80pXFTbU9ZtS
CdvSg9YWvSEz74WpAllNbeUWB7k8Ug2itTgMNjShPrYUY1Q4T/oskDCGy9gU5dG9
H3MCq0XSYLo3A0ChiuL6wc/3eHzMAgqpjsqVznbpI+rvDMb1gwM=
=v1Pl
-----END PGP SIGNATURE-----

--Il7pC/GPZj/XWd6/--