Re: Wrong order of tests in findDependentObjects()

Jim Nasby <jim.nasby@bluetreble.com>

From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, <pgsql-hackers@postgreSQL.org>
Date: 2016-11-27T15:59:30Z
Lists: pgsql-hackers
On 11/26/16 10:25 AM, Tom Lane wrote:
> It suddenly struck me that the problem being complained of in bug #14434
> is that dependency.c's findDependentObjects() is handling extension
> dependencies incorrectly.

I suspect this is unrelated, but I've run into another oddity with 
extension dependency: if an extension creates any temporary objects the 
extension will install and function correctly... until the backend that 
created the extension quits. This is VERY confusing if you've never come 
across it before, because you'll do a bunch of work in a single script 
but when you try to use the extension for real it will "randomly" just 
vanish.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)


Commits

  1. Delete deleteWhatDependsOn() in favor of more performDeletion() flag bits.

  2. Fix some issues with temp/transient tables in extension scripts.