Postgres Pro
Downloads
Home   >   mailing lists

Re: pg_upgrade from 12 to 13 failes with plpython2 - Mailing list pgsql-general

From Bruce Momjian
Subject Re: pg_upgrade from 12 to 13 failes with plpython2
Date
Msg-id 20201118210124.GB13839@momjian.us
Whole thread Raw
In response to Re: pg_upgrade from 12 to 13 failes with plpython2  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_upgrade from 12 to 13 failes with plpython2  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tree view 
On Wed, Nov 18, 2020 at 03:25:56PM -0500, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.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.

It is done that way so we don't overwhelm them with lots of function
names, and they can focus on the library.  I was thinking of showing
them a query that would allow them to investigate.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_upgrade from 12 to 13 failes with plpython2
Next
From: Post Gresql
Date:
Subject: Re: create type with %type or %rowtype