diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2022-07-03 21:38:32 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2022-07-03 21:38:32 -0400 |
commit | 5c1d80ea7797dc4a8e2cdc7e8e62edff50238abe (patch) | |
tree | 0075c2a888d91c375d345610af88c3b0605deab4 /src/backend/executor/nodeProjectSet.c | |
parent | 7d9bf589ba840e9f0167a32226ff91a0b50fed95 (diff) | |
download | postgresql-5c1d80ea7797dc4a8e2cdc7e8e62edff50238abe.tar.gz postgresql-5c1d80ea7797dc4a8e2cdc7e8e62edff50238abe.zip |
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
Diffstat (limited to 'src/backend/executor/nodeProjectSet.c')
0 files changed, 0 insertions, 0 deletions