Re: Support custom socket directory in pg_upgrade - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Support custom socket directory in pg_upgrade
Date
Msg-id 23326.1539094928@sss.pgh.pa.us
Whole thread Raw
In response to Support custom socket directory in pg_upgrade  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Support custom socket directory in pg_upgrade  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Add overflow test in function numeric_exp.
Next
From: Konstantin Knizhnik
Date:
Subject: Re: out-of-order XID insertion in KnownAssignedXids