From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
        Justin Pryzby <pryzby@telsasoft.com>,
        pgsql-hackers@lists.postgresql.org,
        Daniel Gustafsson <daniel@yesql.se>
Subject: Re: format of pg_upgrade loadable_libraries warning
In-reply-to: <20191114221641.GD6160@momjian.us>
References: <20191007174757.GE4732@momjian.us>
 <20191114190652.GA23586@alvherre.pgsql> <20191114221641.GD6160@momjian.us>
Comments: In-reply-to Bruce Momjian <bruce@momjian.us>
	message dated "Thu, 14 Nov 2019 17:16:41 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <17665.1573771752.1@sss.pgh.pa.us>
Date: Thu, 14 Nov 2019 17:49:12 -0500
Message-ID: <17666.1573771752@sss.pgh.pa.us>
Precedence: bulk

Bruce Momjian <bruce@momjian.us> writes:
> 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.

That's better wording, but do we need similar for any of the other
not-supported checks?

			regards, tom lane