Re: Support custom socket directory in pg_upgrade

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Support custom socket directory in pg_upgrade
Date: 2018-11-12 23:46:50
Message-ID: c0cb1bfc-8bca-98d3-ad52-86c14026c266@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-11-12 23:50:27 Re: Support custom socket directory in pg_upgrade
Previous Message David Rowley 2018-11-12 23:17:39 Re: Speeding up INSERTs and UPDATEs to partitioned tables