Re: Finer Extension dependencies - Mailing list pgsql-hackers

From Hitoshi Harada
Subject Re: Finer Extension dependencies
Date
Msg-id CAP7QgmkN080j+cRhu830mg7HCr5eK5sx1RWpLuFF91Np5DXnFw@mail.gmail.com
Whole thread Raw
In response to Re: Finer Extension dependencies  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Responses Re: Finer Extension dependencies  (Hitoshi Harada <umi.tanuki@gmail.com>)
Re: Finer Extension dependencies  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
On Mon, Jan 23, 2012 at 2:00 AM, Dimitri Fontaine
<dimitri@2ndquadrant.fr> wrote:
> Hitoshi Harada <umi.tanuki@gmail.com> writes:
>>>> - What happens if DROP EXTENSION ... CASCADE? Does it work?
>>>
>>> It should, what happens when you try? :)
>>
>> I just tried DROP EXTENSION now, and found it broken :(
>>
>> db1=# create extension kmeans;
>> CREATE EXTENSION
>> db1=# drop extension kmeans;
>> ERROR:  cannot drop extension kmeans because extension feature kmeans
>> requires it
>> HINT:  You can drop extension feature kmeans instead.
>
> Can you provide me the test case you've been using?  That looks like a
> bug I need to fix, indeed (unless the problem lies in the test case,
> which would mean I need to tighten things some more).

The test case is just above; createdb db1 and create and drop an
extension. The kmean extension is on pgxn. I tried my small test
extension named ext1 which contains only one plpgsql function, and
created it then dropped it, reproduced.

Thanks,
--
Hitoshi Harada


pgsql-hackers by date:

Previous
From: Cédric Villemain
Date:
Subject: Re: Inline Extension
Next
From: Marko Kreen
Date:
Subject: Re: Speed dblink using alternate libpq tuple storage