| From: | Enrico Sirola <enrico(dot)sirola(at)gmail(dot)com> |
|---|---|
| To: | Michael Glaesemann <michael(dot)glaesemann(at)myyearbook(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org General" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: unable to drop a constraint |
| Date: | 2008-07-17 09:59:26 |
| Message-ID: | A21641EE-C405-4E3D-95A4-0A024270ECFC@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Michael,
Il giorno 16/lug/08, alle ore 18:21, Michael Glaesemann ha scritto:
>
> On 2008-07-16, at 7:18 AM, Enrico Sirola wrote:
>
>> Hi,
>>
>> I'm using postgresql version 8.3.1
>>
>> I have two tables, one has a field with a foreign key pointing to
>> the primary key of another table. When I to drop the first table, I
>> get the following error:
>>
>> test=# drop table user;
>> ERROR: "customer_pkey" is an index
>
> Are you using slony perchance? This looks like an issue with slony
> blocking DDL operations:
hmmmm I don't use slony anymore, but these tables were part of a
replication set in the past.... It seems a good starting point, thanks
a lot,
e.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | gabrielle | 2008-07-17 14:03:29 | Last chance to sign up for PDXPUG Day! You know you want to! |
| Previous Message | Enrico Sirola | 2008-07-17 09:54:27 | Re: unable to drop a constraint |