Re: "could not open file "pg_wal/…": No such file or directory" potential crashing bug due to race condition between restartpoint and recovery

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Thomas Crayford <tcrayford(at)salesforce(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: "could not open file "pg_wal/…": No such file or directory" potential crashing bug due to race condition between restartpoint and recovery
Date: 2018-10-02 01:06:49
Message-ID: 20181002010649.GS11712@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-10-02 07:52:11 BUG #15415: Can we install OS cluster for PostgreSQL
Previous Message Jerry Sievert 2018-10-01 21:16:30 Re: BUG #15414: extension compilation fails when c++ files are named with .cc