Re: format of pg_upgrade loadable_libraries warning

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: format of pg_upgrade loadable_libraries warning
Date: 2019-11-14 23:32:55
Message-ID: 1053822A-7072-46F3-8569-53EEC21A8966@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 14 Nov 2019, at 23:16, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>
> 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.

I agree with this patch, that's much a more informative message.

There is one tiny typo in the patch: s/laster/later/

+ "cluster, drop them, restart the upgrade, and restore them laster. A\n"

cheers ./daniel

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message imai.yoshikazu@fujitsu.com 2019-11-15 01:00:08 RE: Planning counters in pg_stat_statements (using pgss_store)
Previous Message Tomas Vondra 2019-11-14 23:28:57 Re: Missing dependency tracking for TableFunc nodes