Re: pg_upgrade from 12 to 13 failes with plpython2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Marcin Giedz <marcin(dot)giedz(at)arise(dot)pl>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Magnus Hagander <magnus(at)hagander(dot)net>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Devrim Gündüz <devrim(at)gunduz(dot)org>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_upgrade from 12 to 13 failes with plpython2
Date: 2020-11-18 20:25:56
Message-ID: 1001208.1605731156@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> I think one big problem is that when pg_upgrade fails in this way, users
> are required to do some complex system catalog queries to diagnose the
> cause. Is there a way to simplify this for them?

Maybe pg_upgrade should print the actual function names, not just the
probin values.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2020-11-18 21:01:24 Re: pg_upgrade from 12 to 13 failes with plpython2
Previous Message Bruce Momjian 2020-11-18 20:06:38 Re: pg_upgrade from 12 to 13 failes with plpython2