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

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: "could not open file "pg_wal/…": No such file or directory" potential crashing bug due to race condition betweenrestartpoint and recovery
Дата
Msg-id 20180928225917.GB1823@paquier.xyz
обсуждение исходный текст
Ответ на 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>)
Ответы Re: "could not open file "pg_wal/…": No such file or directory" potential crashing bug due to race condition between restartpoint and recovery
Список pgsql-bugs
On Fri, Sep 28, 2018 at 01:02:42PM +0100, Thomas Crayford wrote:
> Ok, thanks for the pointer. It seems like the race condition I talked about
> is still accurate, does that seem right?

KeepFileRestoredFromArchive() looks like a good candidate on the matter
as it removes a WAL segment before replacing it by another with the same
name.  I have a hard time understanding why the checkpointer would try
to recycle a segment just recovered though as the startup process would
immediately try to use it.  I have not spent more than one hour looking
at potential spots though, which is not much for this kind of race
conditions.

It is also why I am curious about what kind of restore_command you are
using.
--
Michael

Вложения

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Pradeep Singh
Дата:
Сообщение: Regarding "BUG #3995: pqSocketCheck doesn't return"
Следующее
От: PG Bug reporting form
Дата:
Сообщение: BUG #15411: Unable to uninstall