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

From Peter Eisentraut
Subject Re: Support custom socket directory in pg_upgrade
Date
Msg-id c0cb1bfc-8bca-98d3-ad52-86c14026c266@2ndquadrant.com
Whole thread Raw
In response to Re: Support custom socket directory in pg_upgrade  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Support custom socket directory in pg_upgrade  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 12/11/2018 20:00, Tom Lane wrote:
> Also, even if we had an arguably-better idea, I suspect that there would
> always be cases where it didn't work.  For example, one idea is to make
> a temporary directory under the installation's normal socket directory
> (thus, /tmp/pgXXXX/ or some such).  But, if the normal socket directory
> is not /tmp, we might find that pg_upgrade can't write there.

We do exactly that in pg_regress and it's never been a problem.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Speeding up INSERTs and UPDATEs to partitioned tables
Next
From: Tom Lane
Date:
Subject: Re: Support custom socket directory in pg_upgrade