Re: Concurrency issue in pg_rewind

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Concurrency issue in pg_rewind
Дата
Msg-id 20200918065945.GD2772@paquier.xyz
обсуждение исходный текст
Ответ на Re: Concurrency issue in pg_rewind  ("Andrey M. Borodin" <x4mmm@yandex-team.ru>)
Ответы Re: Concurrency issue in pg_rewind
Re: Concurrency issue in pg_rewind
Список pgsql-hackers
On Fri, Sep 18, 2020 at 11:31:26AM +0500, Andrey M. Borodin wrote:
> This is whole point of having prefetch. restore_command just links
> file from the same partition.

If this stuff is willing to do so, you may have your reasons, but even
if you wish to locate both pg_wal/ and the prefetch path in the same
partition, I don't get why it is necessary to have the prefetch path
included directly in pg_wal?  You could just use different paths for
both.  Say, with a base partition at /my/path/, you can just have
/my/path/pg_wal/ that the Postgres backend links to, and
/my/path/wal-g/prefetch/ for the secondary path.
--
Michael

Вложения

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

Предыдущее
От: "Andrey M. Borodin"
Дата:
Сообщение: Re: Concurrency issue in pg_rewind
Следующее
От: Alexander Kukushkin
Дата:
Сообщение: Re: Concurrency issue in pg_rewind