| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_basebackup check vs Windows file path limits |
| Date: | 2023-07-04 20:54:54 |
| Message-ID: | 67093EFC-3800-48B0-9E20-82A37A5F2A7B@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2023-07-04 21:32:07 | Re: PG 16 draft release notes ready |
| Previous Message | Melih Mutlu | 2023-07-04 20:18:14 | Re: [PATCH] Reuse Workers and Replication Slots during Logical Replication |