public inbox for [email protected]
help / color / mirror / Atom feedFrom: Andrew Dunstan <[email protected]>
To: PostgreSQL-development <[email protected]>
Subject: Re: pg_basebackup check vs Windows file path limits
Date: Mon, 3 Jul 2023 10:12:49 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
On 2023-07-02 Su 09:15, Andrew Dunstan wrote:
>
> 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.
>
I've pushed a better solution, which creates the file via a short
symlink. Experimentation on fairywren showed this working.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
view thread (6+ messages) latest in thread
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