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

From Daniel Gustafsson
Subject Support custom socket directory in pg_upgrade
Date
Msg-id E72DD5C3-2268-48A5-A907-ED4B34BEC223@yesql.se
Whole thread Raw
Responses Re: Support custom socket directory in pg_upgrade  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Support custom socket directory in pg_upgrade  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
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?

cheers ./daniel


Attachment

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Refactor textToQualifiedNameList()
Next
From: Arun Kumar
Date:
Subject: Requesting advanced Group By support