Re: Support custom socket directory in pg_upgrade

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Daniel Gustafsson <daniel@yesql.se>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2018-10-09T14:22:08Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add a --socketdir option to pg_upgrade.
- 2d34ad843031 12.0 landed

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