Re: support for windows robocopy in archive_command and restore_command

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
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 03:25:50
Message-ID: b7f894ad-c1ea-8102-6028-f42c19a95d3f@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 8/18/21 10:32 PM, Julien Rouhaud wrote:
> 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?

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2021-08-19 03:28:07 Re: [PATCH]Remove obsolete macro CHECKFLOATVAL in btree_gist
Previous Message Tom Lane 2021-08-19 03:08:57 Re: strange case of "if ((a & b))"