Re: pg_upgrade and missing loadable libraries

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade and missing loadable libraries
Date: 2017-06-04 18:30:58
Message-ID: 12858.1496601058@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> I didn't want to optimize for it --- I wanted a way to detect when DROP
> EXTENSION has no hope of working, and give more details. I assume the
> problem with that is the the object names are inside SQL scripts that
> cannot be easily interrogated. Are the pg_proc entries tied to the
> extension in some verifiable way that we could identify orphaned pg_proc
> lines?

You could look for 'e'-type pg_depend entries.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Beena Emerson 2017-06-04 18:36:30 Re: Adding support for Default partition in partitioning
Previous Message Bruce Momjian 2017-06-04 18:16:32 Re: pg_upgrade and missing loadable libraries