| 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 21:45:24 |
| Message-ID: | 1004475.1605735924@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:
> On Wed, Nov 18, 2020 at 03:25:56PM -0500, Tom Lane wrote:
>> 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.
These days "focus on the extension" would be more helpful. Maybe
we could check to see if all the functions referencing a given .so
belong to the same extension, and if so complain about that extension?
I think there's a reasonable argument that functions that don't
belong to any known extension should be printed individually,
because more than likely the user's gonna have to clean them up
manually, as we saw here.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Devrim Gündüz | 2020-11-18 22:06:17 | Re: pg_upgrade from 12 to 13 failes with plpython2 |
| Previous Message | Post Gresql | 2020-11-18 21:08:11 | Re: create type with %type or %rowtype |