| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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 21:01:24 |
| Message-ID: | 20201118210124.GB13839@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Nov 18, 2020 at 03:25:56PM -0500, Tom Lane wrote:
> 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.
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(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Post Gresql | 2020-11-18 21:08:11 | Re: create type with %type or %rowtype |
| Previous Message | Tom Lane | 2020-11-18 20:25:56 | Re: pg_upgrade from 12 to 13 failes with plpython2 |