public inbox for [email protected]  

help / color / mirror / Atom feed

From: Andrew Dunstan <[email protected]>
To: PostgreSQL-development <[email protected]>
Subject: pg_basebackup check vs Windows file path limits
Date: Sun, 2 Jul 2023 09:15:17 -0400
Message-ID: <[email protected]> (raw)


The buildfarm animal fairywren has been failing the tests for 
pg_basebackup because it can't create a file with a path longer than 255 
chars. This has just been tripped because for release 16 it's running 
TAP tests, and the branch name is part of the file path, and 
"REL_16_STABLE" is longer than "HEAD". I did think of chdir'ing into the 
directory to create the file, but experimentation shows that doesn't 
solve matters. I also adjusted the machine's settings related to long 
file names, but to no avail, so for now I propose to reduce slightly the 
name of the long file so it still exercises the check for file names 
longer than 100 but doesn't trip this up on fairywren. But that's a 
bandaid. I don't have a good solution for now.


cheers


andrew

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

view thread (2+ messages)

reply

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: [email protected]
  Cc: [email protected]
  Subject: Re: pg_basebackup check vs Windows file path limits
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox