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 d4b3e53a-6efd-b1f5-091c-ac02ae60e631@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 30/11/2018 17:58, Tom Lane wrote:
> So we seem to be at an impasse here.  By my count, three people have
> expressed support for the patch's approach of adding a socket-directory
> option, while two people seem to prefer the idea of putting pg_upgrade's
> socket under /tmp (possibly with a way to override that).  That's not
> enough of a consensus to proceed with either approach, really, but
> we ought to do something because the problem is real.
> 
> Given that we have a patch for this approach, and no patch has been
> offered for the /tmp approach, I'm kind of inclined to exercise
> committer's discretion and proceed with this patch.  Will anybody
> be seriously annoyed if I do?

I think it's fair to proceed and leave open that someone submits a
(possibly) better patch for a different approach in the future.

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


pgsql-hackers by date:

Previous
From: Dmitry Dolgov
Date:
Subject: Re: [HACKERS] WAL logging problem in 9.4.3?
Next
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] proposal - Default namespaces for XPath expressions(PostgreSQL 11)