Re: Wrong order of tests in findDependentObjects()

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Wrong order of tests in findDependentObjects()
Date: 2016-11-27 15:59:30
Message-ID: e51f4311-f483-4dd0-1ccc-abec3c405110@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-11-27 16:15:01 Re: Wrong order of tests in findDependentObjects()
Previous Message Amos Bird 2016-11-27 15:39:49 Re: make default TABLESPACE belong to target table.