Re: "could not open file "pg_wal/…": No such file or directory" potential crashing bug due to race condition betweenrestartpoint and recovery - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: "could not open file "pg_wal/…": No such file or directory" potential crashing bug due to race condition betweenrestartpoint and recovery
Date
Msg-id 20181002010649.GS11712@paquier.xyz
Whole thread Raw
In response to Re: "could not open file "pg_wal/…": No such file or directory" potential crashing bug due to race condition between restartpoint and recovery  (Thomas Crayford <tcrayford@salesforce.com>)
List pgsql-bugs
On Mon, Oct 01, 2018 at 12:43:02PM +0100, Thomas Crayford wrote:
> Sorry for the slow response on this - I was oncall last week and it was
> quite distracting and busy.
>
> With respect to the restore_command, we use wal-e:
> https://github.com/wal-e/wal-e, specifically:
>
> envdir DIRECTORY wal-e wal-fetch "%f" "%p"

Okay, so that should be fine.  When it comes to such race conditions,
putting directly into the suspicious code paths calls to pg_usleep would
most likely help in enforcing the bug to show up.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Jerry Sievert
Date:
Subject: Re: BUG #15414: extension compilation fails when c++ files are namedwith .cc
Next
From: PG Bug reporting form
Date:
Subject: BUG #15415: Can we install OS cluster for PostgreSQL