From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
---|---|
To: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
Cc: | gary(dot)haran(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #6718: Cannot delete, create or check existence of extension |
Date: | 2012-07-05 15:09:39 |
Message-ID: | 4FF5AE33.5010800@ringerc.id.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 07/05/2012 10:18 PM, Jaime Casanova wrote:
> On Thu, Jul 5, 2012 at 1:56 AM, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> wrote:
>> On 07/05/2012 02:05 AM, gary(dot)haran(at)gmail(dot)com wrote:
>>> development=# create extension hstore;
>>> ERROR: type "hstore" already exists
>> First, thanks for the info in the report.
>>
>> At a guess, it has the hstore data type in it from before the extension
>> system exists. You need to follow the upgrade instructions to convert it to
>> an extension.
> what about adding a HINT there? something like "you probably need to
> use CREATE EXTENSION ... FROM unpackaged"
>
Yeah, I suggested that. It's not trivial to make sure that this is
really because of the extension and not because the user just happened
to create their own type called "hstore" (or whatever the
type(s)/function(s) the ext provides) are, but I guess with a hint you
don't have to. I'm assuming if it were simple it would've been done as
part of extension implementation. It's certainly way beyond me.
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Payal Singh | 2012-07-05 15:20:44 | Problem with pg_upgrade |
Previous Message | Jaime Casanova | 2012-07-05 14:18:11 | Re: BUG #6718: Cannot delete, create or check existence of extension |