Re: pg_basebackup check vs Windows file path limits

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_basebackup check vs Windows file path limits
Date: 2023-07-05 12:49:39
Message-ID: 0c1c289c-f55a-1cc3-4ce1-44d7e8353e70@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2023-07-04 Tu 16:54, Daniel Gustafsson wrote:
>> On 4 Jul 2023, at 20:19, Andrew Dunstan<andrew(at)dunslane(dot)net> wrote:
>> But sadly we're kinda back where we started. fairywren is failing on REL_16_STABLE. Before the changes the failure occurred because the test script was unable to create the file with a path > 255. Now that we have a way to create the file the test for pg_basebackup to reject files with names > 100 fails, I presume because the server can't actually see the file. At this stage I'm thinking the best thing would be to skip the test altogether on windows if the path is longer than 255.
> That does sound like a fairly large hammer for a nail small enough that we
> should be able to fix it, but I don't have any other good ideas off the cuff.

Not sure it's such a big hammer. Here's a patch.

cheers

andrew

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

Attachment Content-Type Size
pg_basebackup-long-file-fix.patch text/x-patch 1.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2023-07-05 13:22:30 Re: [PATCH] Add GitLab CI to PostgreSQL
Previous Message Amit Kapila 2023-07-05 12:47:54 Re: logicalrep_message_type throws an error