Daniel Gustafsson <daniel@yesql.se> writes:
> Having hit the maximum socketdir length error a number of times in pg_upgrade,
> especially when running tests in a deep directory hierarchy, I figured it was
> time to see if anyone else has had the same problem? The attached patch is
> what I run with locally to avoid the issue, it adds a --socketdir=PATH option
> to pg_upgrade which overrides the default use of CWD. Is that something that
> could be considered?
I think you could simplify matters if you installed the CWD default value
during option processing.
regards, tom lane