pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Ярослав Пашинский <yarik97.6@gmail.com>
Cc: Postgres bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #16927: Postgres can`t access WAL files
Date: Fri, 19 Mar 2021 17:28:07 +0900
Message-ID: <YFRglwF+j2RMmbXF@paquier.xyz> (raw)
In-Reply-To: <CADLmTo+GoZ1tuyZxx5uprqSkwqqw3yajry36o-+=N=Jqe=0oZA@mail.gmail.com>
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>

On Fri, Mar 19, 2021 at 10:08:36AM +0200, Ярослав Пашинский 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

Attachments:

  [application/pgp-signature] signature.asc (832B, ../YFRglwF+j2RMmbXF@paquier.xyz/2-signature.asc)
  download

view thread (29+ messages)  latest in thread

Message-ID: <YFRglwF+j2RMmbXF@paquier.xyz>
Permalink:  ../YFRglwF+j2RMmbXF@paquier.xyz/
Also on:    postgresql.org/message-id/YFRglwF+j2RMmbXF@paquier.xyz

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: michael@paquier.xyz, yarik97.6@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #16927: Postgres can`t access WAL files
  In-Reply-To: <YFRglwF+j2RMmbXF@paquier.xyz>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox