pgsql: Skip pg_baseback long filename test if path too long on Windows

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Skip pg_baseback long filename test if path too long on Windows
Date: 2023-07-06 16:37:55
Message-ID: E1qHRzP-002Dwd-Kd@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Skip pg_baseback long filename test if path too long on Windows

On Windows, it's sometimes difficult to create a file with a path longer
than 255 chars, and if it can be created it might not be seen by the
archiver. This can be triggered by the test for tar backups with
filenames greater than 100 bytes. So we skip that test if the path would
exceed 255.

Backpatch to all live branches.

Reviewed by Daniel Gustafsson

Discussion: https://postgr.es/m/666ac55b-3400-fb2c-2cea-0281bf36a53c@dunslane.net

Branch
------
REL_15_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/c0cb12f9e7b33bbcd64cc93d0811bc10e17e5452

Modified Files
--------------
src/bin/pg_basebackup/t/010_pg_basebackup.pl | 28 +++++++++++++++-------------
1 file changed, 15 insertions(+), 13 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Nathan Bossart 2023-07-06 17:20:04 Re: pgsql: Fix search_path to a safe value during maintenance operations.
Previous Message Heikki Linnakangas 2023-07-06 14:30:12 pgsql: WAL-log the creation of the init fork of unlogged indexes.