Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1h7GkD-0004cb-Dj
	for pgsql-hackers@arkaria.postgresql.org; Fri, 22 Mar 2019 09:45:45 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1h7GkC-0002fx-0m
	for pgsql-hackers@arkaria.postgresql.org; Fri, 22 Mar 2019 09:45:44 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <cb@df7cb.de>)
	id 1h7GkB-0002fe-PZ
	for pgsql-hackers@lists.postgresql.org; Fri, 22 Mar 2019 09:45:43 +0000
Received: from feynman.df7cb.de ([195.49.152.168])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <cb@df7cb.de>)
	id 1h7Gk9-0000pD-I0
	for pgsql-hackers@lists.postgresql.org; Fri, 22 Mar 2019 09:45:43 +0000
Received: from msg.df7cb.de (unknown
 [IPv6:2003:5b:203b:100:7627:eaff:fe52:8e03])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client did not present a certificate)
	by feynman.df7cb.de (Postfix) with ESMTPSA id 44Qf0h2N6Zz3F0Q;
	Fri, 22 Mar 2019 10:45:40 +0100 (CET)
Date: Fri, 22 Mar 2019 10:45:40 +0100
From: Christoph Berg <myon@debian.org>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@lists.postgresql.org,
	Tomasz Szypowski <tomasz.szypowski@gmail.com>
Subject: Re: pg_upgrade version checking questions
Message-ID: <20190322094539.GB32388@msg.df7cb.de>
References: <9328.1552952117@sss.pgh.pa.us>
 <b659c1df-c37a-52da-da7f-e0659c34c92a@2ndquadrant.com>
 <13426.1553010710@sss.pgh.pa.us>
 <57769959-8960-a9ca-fc9c-4dbb12629b8a@2ndquadrant.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <57769959-8960-a9ca-fc9c-4dbb12629b8a@2ndquadrant.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Precedence: bulk

Re: Peter Eisentraut 2019-03-22 <57769959-8960-a9ca-fc9c-4dbb12629b8a@2ndquadrant.com>
> I'm still in favor of defaulting --new-bindir appropriately.  It seems
> silly not to.  We know where the directory is, we don't have to ask anyone.

Fwiw I've been wondering why I have to pass that option every time
I've been using pg_upgrade. +1 on making it optional/redundant.

Christoph