From: Andrew Dunstan <andrew@dunslane.net>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Improve pg_basebackup long file name test Windows robustness
Date: Mon, 03 Jul 2023 14:08:45 +0000
Message-ID: <E1qGKEP-001iBZ-5q@gemulon.postgresql.org> (raw)
Improve pg_basebackup long file name test Windows robustness
Creation of a file with a very long name can create problems on Windows
due to its file path limits. Work around that by creating the file via a
symlink with a shorter name.
Error displayed by buildfarm animal fairywren.o
Backpatch to all live branches
Branch
------
REL_12_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/088e395c8ae06047784c41b08c54d526d00517c9
Modified Files
--------------
src/bin/pg_basebackup/t/010_pg_basebackup.pl | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: andrew@dunslane.net, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Improve pg_basebackup long file name test Windows robustness
In-Reply-To: <E1qGKEP-001iBZ-5q@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox