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: Wed, 17 Mar 2021 08:56:01 +0900
Message-ID: <YFFFkWzunPO9M6kV@paquier.xyz> (raw)
In-Reply-To: <YFExaMohbb8tqM3k@paquier.xyz>
References: <16927-67c570d968c99567@postgresql.org>
	<YFAH1LbeUeXTFcEM@paquier.xyz>
	<CADLmToLD6a=eXvh+b6u+Ju5Bm2ZvtCHBnCqY_d8U9we+315HZg@mail.gmail.com>
	<YFBu8b4dH32kQwDG@paquier.xyz>
	<CADLmTo+Kb0EzCFH1yYdjKneQYG=OsEX4=naAjaHOAeeNmY=HLA@mail.gmail.com>
	<YFCF+JbyfObn5zPu@paquier.xyz>
	<CADLmTo+gkFJ9or_Mfp6KKEj9MAip_BgHG6A9mzxR1DMpuRp3fg@mail.gmail.com>
	<YFExaMohbb8tqM3k@paquier.xyz>

On Wed, Mar 17, 2021 at 07:30:00AM +0900, Michael Paquier wrote:
> I am still running some tests on my own environments, but that's much
> harder to hit for me, visibly, and the error code path complaining is
> not the same.  If I may ask, what are the contents of pg_wal on the
> instances where the errors happen.  Do you have some files suffixed
> with ".deleted" around, or anything named like xlogtemp.N, where N is
> an integer for a PID?

Another thing I could do here is to share links to download all the
binaries built for 13.2 and 13.2 + a patch, that you could drop into
your own servers to test what I am suspecting causes the issue.
Depending on your server policies, perhaps that's not acceptable,
though.  Just let me know which one you'd prefer.
--
Michael

Attachments:

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

view thread (29+ messages)  latest in thread

Message-ID: <YFFFkWzunPO9M6kV@paquier.xyz>
Permalink:  ../YFFFkWzunPO9M6kV@paquier.xyz/
Also on:    postgresql.org/message-id/YFFFkWzunPO9M6kV@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: <YFFFkWzunPO9M6kV@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