Re: Wrong order of tests in findDependentObjects()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Wrong order of tests in findDependentObjects()
Date: 2016-11-27 16:15:01
Message-ID: 5774.1480263301@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> writes:
> 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.

Yeah, I was wondering about that yesterday --- that comment mentions
the case of temporary objects, but it only fixes the problem while the
script runs. Maybe there should be a separate test for "we're doing
temporary-object cleanup" that would similarly prevent recursion to
an extension?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-11-27 16:29:33 Re: RFC Changing the version number for JDBC
Previous Message Jim Nasby 2016-11-27 15:59:30 Re: Wrong order of tests in findDependentObjects()