Support custom socket directory in pg_upgrade

Daniel Gustafsson <daniel@yesql.se>

From: Daniel Gustafsson <daniel@yesql.se>

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

Date: 2018-10-09T13:09:25Z

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

Attachments

pg_upgrade_sockdir.patch (application/octet-stream) patch

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