Re: support for windows robocopy in archive_command and restore_command

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: support for windows robocopy in archive_command and restore_command
Date: 2021-08-19 02:32:15
Message-ID: CAOBaU_Y-qaQOqZux5Aq9sbUeJ+W2TwHeTt_X-VEEcpNYTL5fGw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 19, 2021 at 5:01 AM Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> It doesn't allow for files to be renamed, but luckily we don't normally
> need it to.

Doesn't the recovery ask to recover the WAL files in
pg_wal/RECOVERYXLOG and the history files in pg_wal/RECOVERYHISTORY
rather than the original names?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bossart, Nathan 2021-08-19 02:46:19 Re: archive status ".ready" files may be created too early
Previous Message Masahiko Sawada 2021-08-19 01:53:01 Re: Skipping logical replication transactions on subscriber side