Re: [HACKERS] pg_upgrade and missing loadable libraries - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] pg_upgrade and missing loadable libraries
Date
Msg-id 20170604192854.GF2672@momjian.us
Whole thread Raw
In response to Re: [HACKERS] pg_upgrade and missing loadable libraries  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Jun  4, 2017 at 02:30:58PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.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.

OK, I will run some tests later and report back.  Thanks.

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

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +



pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: [HACKERS] PostgreSQL 10 changes in exclusion constraints - did something change? CASE WHEN behavior oddity
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] PostgreSQL 10 changes in exclusion constraints - didsomething change? CASE WHEN behavior oddity