Re: support for windows robocopy in archive_command and restore_command - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: support for windows robocopy in archive_command and restore_command
Date
Msg-id b7f894ad-c1ea-8102-6028-f42c19a95d3f@dunslane.net
Whole thread Raw
In response to Re: support for windows robocopy in archive_command and restore_command  (Julien Rouhaud <rjuju123@gmail.com>)
List pgsql-hackers
On 8/18/21 10:32 PM, Julien Rouhaud wrote:
> On Thu, Aug 19, 2021 at 5:01 AM Andrew Dunstan <andrew@dunslane.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?


Oh, darn. I was looking at what pg_rewind does; it uses the same name.


Well, maybe we need to scrub that idea -(


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: strange case of "if ((a & b))"
Next
From: Michael Paquier
Date:
Subject: Re: [PATCH]Remove obsolete macro CHECKFLOATVAL in btree_gist