Use a short socket directory path in pg_upgrade testing.
Tom Lane <tgl@sss.pgh.pa.us>
Use a short socket directory path in pg_upgrade testing. Several buildfarm members are failing the pg_upgrade test in REL_15_STABLE, though the identical test is fine in HEAD. On thorntail it's possible to see that the problem is an overlength socket path name, and I bet the same is true on the others. The normally-started postmasters used in the test are already set up with short socket directory paths, but we neglected to tell pg_upgrade itself to do likewise when starting child postmasters, and indeed it seems to be explicitly selecting the test directory instead. Back-patch to v15 where the current test script was introduced. (The previous script might have the same issue, because I don't see any use of -s/--socketdir in it either; but we've had no complaints, so leave it alone for now.) Discussion: https://postgr.es/m/1410025.1656890531@sss.pgh.pa.us
Files
| Path | Change | +/− |
|---|---|---|
| src/bin/pg_upgrade/t/002_pg_upgrade.pl | modified | +6 −4 |
Discussion
- Too-long socket paths are breaking several buildfarm members 4 messages · 2022-07-03 → 2022-07-04