Re: Support custom socket directory in pg_upgrade

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

Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> 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.

Yeah, but pg_upgrade is used by a much wider variety of people
than pg_regress.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-11-12 23:53:21 Re: [HACKERS] Decimal64 and Decimal128
Previous Message Peter Eisentraut 2018-11-12 23:46:50 Re: Support custom socket directory in pg_upgrade