| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>, Alexander Kukushkin <cyberdemn(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Concurrency issue in pg_rewind |
| Date: | 2020-09-18 06:59:45 |
| Message-ID: | 20200918065945.GD2772@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Kukushkin | 2020-09-18 07:17:23 | Re: Concurrency issue in pg_rewind |
| Previous Message | Andrey M. Borodin | 2020-09-18 06:31:26 | Re: Concurrency issue in pg_rewind |