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 ) id 1iVNQ2-00046V-LZ for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Nov 2019 22:16:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iVNQ1-0003qh-3R for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Nov 2019 22:16:49 +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 ) id 1iVNQ0-0003qa-Qn for pgsql-hackers@lists.postgresql.org; Thu, 14 Nov 2019 22:16:48 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iVNPx-00005V-UF for pgsql-hackers@lists.postgresql.org; Thu, 14 Nov 2019 22:16:48 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1iVNPt-0002nw-Rz; Thu, 14 Nov 2019 17:16:41 -0500 Date: Thu, 14 Nov 2019 17:16:41 -0500 From: Bruce Momjian To: Alvaro Herrera Cc: Tom Lane , Justin Pryzby , pgsql-hackers@lists.postgresql.org, Daniel Gustafsson Subject: Re: format of pg_upgrade loadable_libraries warning Message-ID: <20191114221641.GD6160@momjian.us> References: <20191007174757.GE4732@momjian.us> <20191114190652.GA23586@alvherre.pgsql> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="azLHFNyN32YCQGCU" Content-Disposition: inline In-Reply-To: <20191114190652.GA23586@alvherre.pgsql> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Nov 14, 2019 at 04:06:52PM -0300, Alvaro Herrera wrote: > BTW, how is one supposed to "manually upgrade databases that use > contrib/isb"? This part is not very clear. I thought you would dump out databases that use isn, drop those databases, use pg_upgrade for the remaining databases, then load the dumped database. Attached is a patch that improves the wording. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + --azLHFNyN32YCQGCU Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="isn.diff" diff --git a/src/bin/pg_upgrade/check.c b/src/bin/pg_upgrade/check.c index ff7057db73..e5f1c64799 100644 --- a/src/bin/pg_upgrade/check.c +++ b/src/bin/pg_upgrade/check.c @@ -887,9 +887,9 @@ check_for_isn_and_int8_passing_mismatch(ClusterInfo *cluster) pg_fatal("Your installation contains \"contrib/isn\" functions which rely on the\n" "bigint data type. Your old and new clusters pass bigint values\n" "differently so this cluster cannot currently be upgraded. You can\n" - "manually upgrade databases that use \"contrib/isn\" facilities and remove\n" - "\"contrib/isn\" from the old cluster and restart the upgrade. A list of\n" - "the problem functions is in the file:\n" + "manually dump databases that use \"contrib/isn\" facilities in the old\n" + "cluster, drop them, restart the upgrade, and restore them laster. A\n" + "list of the problem functions is in the file:\n" " %s\n\n", output_path); } else --azLHFNyN32YCQGCU--