Re: Finding database for pg_upgrade missing library - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Finding database for pg_upgrade missing library
Date
Msg-id C9FA19EB-C97A-45C5-AA32-C476E5F8D82B@yesql.se
Whole thread Raw
In response to Finding database for pg_upgrade missing library  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Finding database for pg_upgrade missing library  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
> On 13 Jul 2018, at 18:28, Bruce Momjian <bruce@momjian.us> wrote:
>
> I received a private pg_upgrade feature request to report the database
> name for missing loadable libraries.  Currently we report "could not
> load library" and the library file name, e.g. $libdir/pgpool-regclass.
>
> The request is that we report the _database_ name that contained the
> loadable library reference.  However, that isn't easy to do because we
> gather all loadable library file names, sort them, and remove
> duplicates, for reasons of efficiency and so we check libraries in a
> predictable alphabetical order.
>
> Is it worth modifying pg_upgrade to report the first or all databases
> that contain references to missing loadable libraries?  I don't think
> so, but I wanted to ask here.

I ran into that very problem when upgrading 50+ clusters during a long night a
while back, and patched pg_upgrade to report the database which helped a lot
(or at least helped me be a bit lazy).  So, +1 on the feature from me.  If
there is interest I can see if I can dig out the patch and polish it up.

cheers ./daniel

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: GSOC 2018 Project - A New Sorting Routine
Next
From: Andrew Dunstan
Date:
Subject: Re: cannot restore schema with is not distinct from on hstore sincePG 9.6.8