Date: Fri, 19 Mar 2021 17:28:07 +0900
From: Michael Paquier <michael@paquier.xyz>
To: =?utf-8?B?0K/RgNC+0YHQu9Cw0LIg0J/QsNGI0LjQvdGB0LrQuNC5?=
 <yarik97.6@gmail.com>
Cc: Postgres bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #16927: Postgres can`t access WAL files
Message-ID: <YFRglwF+j2RMmbXF@paquier.xyz>
References: 
 <CADLmToLRCck9P7k=iOzLZRU7FiUmFTTTTggxF3gc0a1RasYrhQ@mail.gmail.com>
 <YFKB0ccg5zN+nS0Z@paquier.xyz>
 <CADLmToKd=eFW9E+p7i0sxHOZZKshShvJSedD3ek=+PqhiXt4jg@mail.gmail.com>
 <YFMTgN8KY9MQsiIk@paquier.xyz>
 <CADLmTo+FaWQEi9Lt=f4kc9wL-XT+RiaEddW2kfuCZ=XiXycwNQ@mail.gmail.com>
 <CADLmTo+AOq2UE3Gr22omfcxhZajqkeGYgWFowKNScOZA1fWVFA@mail.gmail.com>
 <YFM2MRbHZGQ4DsG/@paquier.xyz>
 <CADLmToJJykdGUdKiPkut4mq8oZJ8z4+8d5aSUU9zCtey7yu_9g@mail.gmail.com>
 <YFPMl3TUPXbN127E@paquier.xyz>
 <CADLmTo+GoZ1tuyZxx5uprqSkwqqw3yajry36o-+=N=Jqe=0oZA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="siYxMOn9gYsPCInO"
Content-Disposition: inline
In-Reply-To: 
 <CADLmTo+GoZ1tuyZxx5uprqSkwqqw3yajry36o-+=N=Jqe=0oZA@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/YFRglwF%2Bj2RMmbXF%40paquier.xyz>
Precedence: bulk


--siYxMOn9gYsPCInO
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Mar 19, 2021 at 10:08:36AM +0200, =D0=AF=D1=80=D0=BE=D1=81=D0=BB=D0=
=B0=D0=B2 =D0=9F=D0=B0=D1=88=D0=B8=D0=BD=D1=81=D0=BA=D0=B8=D0=B9 wrote:
> Yes, for this moment I have 4 clusters on developer server and 1 cluster
> that I`m testing by my own and there is no error connected with
> access to WAL files for last about 17-20 hours. I`ll will run my prod
> clusters and will also tell you. If I won`t send you any new message - the
> problem is gone also on prod server. Thanks in advance!

Cool.  So, it really looks like we have found the issue based on what
you are saying here, and that we had better consider as a first step a
revert of aaaef7a on HEAD and REL_13_STABLE.

So, what do others think?  Would people agree to revert aaaef7a for
now?

> P.S: the error "2021-03-18 12:22:26.096 EET [4840] LOG:  could not rename
> temporary statistics file "pg_stat_tmp/global.tmp" to
> "pg_stat_tmp/global.stat": Permission denied" still be, as I know it`s not
> very

This one is in a different code path.

> P.S.S: will be this patch available to download for everyone?

Well, if a different committer or myself is able to get a patch
committed, it will available to everyone once 13.3 gets released.
This would happen in May based on the existing roadmap:
https://www.postgresql.org/developer/roadmap/

How much did you test the unpatched builds by the way?
--
Michael

--siYxMOn9gYsPCInO
Content-Type: application/pgp-signature; name="signature.asc"

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

iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmBUYJcACgkQnvQgOdby
QH1tWA//fLP25tALdgsMY66oZQGM2BwMbpeZo6cCsXQ9EsRK4pnM8sgKNfqWBp2T
k3f2h9EMZ1uLvLCbRTM0ZEo2FOYfctV6Tk/1CmGuszXnh9LRIuVYDsQUpx+ClW/C
+rBC48IlsvKZUCiUu8tdnR9TzbYo+SdXjnPoGTXNdSsTx4Edt9orGOtfEVQlIkNC
ttcwmTmh5nK2xfeq71SBLvgCSDltqECBUaCTYXMn5QO2UMgfjNnTjjLYb2AW7pA3
AKFHs4w8t7zYsPxMub89rhN0YPh1GxIXhIBKLC0dXI+3uGaEblzIi9oHssADTwfR
Z+VWAEaiZOh7Z1rsq/3TePdpnEZXq7hIa2wT3R/ud+lM00ZrIXyVnymnYrbLuUHM
T0ACjPgXOD12Y3JiB97ancZYwvgU4R2CjbVh9dAdnki6ullncfTXHZGdea4w2aJ1
LCuCK7qwxoUjg2dGWs3wglTs3JLlnuopcut8a86T/Qo29E/j7dFGyYJTyEBoAPm/
7SkwQmpO0b+ZauGcJtUMglo3/UGmrmMSZcVaTFtZw+PO18Fy2bbUvnPB1pnif6Up
Wqnh7FFvUWoc5/RDqQndLXHB9Vqk/sngsZkRfk3FqFxAZKr1qi1jEB70uwsQ6Q+Z
+feBQa7rGli3hbDMk6+tJ9cO16FMrK9QsK8SAGjE3sBR8ZceMx4=
=Nw7P
-----END PGP SIGNATURE-----

--siYxMOn9gYsPCInO--