From: | Brian Hirt <bhirt(at)mobygames(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | can't drop table |
Date: | 2005-09-10 20:19:43 |
Message-ID: | 9689B4E5-ABB1-4A48-8477-35E3A056E7D6@mobygames.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm a bit baffled by this, i can't drop a table and I'm getting the
most bizarre message that doesn't make sense to me. To make things
worse, I was able to drop it on my test database which is a dump of
my production database running the same version of postgresql.
The index it's complaining about is the primary for a different table.
Does anyone have any ideas?
basement=# \d game_giveaway
Table "public.game_giveaway"
Column | Type | Modifiers
---------------------+---------
+--------------------------------------------------------
game_giveaway_id | integer | not null default nextval
('game_giveaway_id_seq'::text)
game_id | integer |
description | text |
date_placed_on_list | date |
date_given_away | date |
given_to_user_id | integer |
Indexes:
"game_giveaway_pkey" PRIMARY KEY, btree (game_giveaway_id)
basement=# drop TABLE public.game_giveaway ;
ERROR: "game_pkey" is an index
basement=# select version();
version
------------------------------------------------------------------------
---------------------------------
PostgreSQL 8.0.3 on i686-pc-linux-gnu, compiled by GCC gcc (GCC)
3.3.2 20031022 (Red Hat Linux 3.3.2-1)
(1 row)
basement=#
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2005-09-10 20:31:14 | Re: EMS PostgreSQL Manager vs. TheKompany DataArchitect |
Previous Message | Tino Wildenhain | 2005-09-10 20:09:14 | Re: Returning XML with SELECT statements? IS THIS |