From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Raymond Chui <raymond.chui@noaa.gov>
Cc: pgsql-general@postgresql.org
Cc: pgsql-admin@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: Why table has drop, but the foreign key still there?
Date: Wed, 13 Aug 2003 12:38:29 -0700 (PDT)
Message-ID: <20030813123631.I55790-100000@megazone.bigpanda.com> (raw)
In-Reply-To: <3F3A8010.9030701@noaa.gov>
On Wed, 13 Aug 2003, Raymond Chui wrote:
>
> Here are the simple things I did
>
> create table state (
> state_code char(2) not null,
> state varchar(15) not null,
> primary key (state_code)
> );
>
> create table whitepage (
> user_id char(8) not null,
> email varchar(50),
> telephone char(16) not null,
> contact_name varchar(30) not null,
> city varchar(20),
> state_code char(2),
> primary key (user_id),
> foreign key (state_code) references state (state_code)
> );
>
>
> insert into state (state_code,state) values ('GU','Guam');
> drop table whitepage;
> delete from state where state_code = 'GU';
> ERROR: Relation "whitepage" does not exist
What version are you using? I can't seem to replicate this given the
above on 7.2, 7.3 or 7.4.
If these tables were preexisting and had gone through a dump cycle
from 7.0 or 7.1, there was a bug in pg_dump for those versions that
would lose the connection between the triggers and the other table
of the constraint.
In any case, you'll need to find and drop the two orphaned triggers on
state (see techdocs for information on how to find them).
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: sszabo@megazone.bigpanda.com, raymond.chui@noaa.gov, pgsql-general@postgresql.org, pgsql-admin@postgresql.org
Subject: Re: Why table has drop, but the foreign key still there?
In-Reply-To: <20030813123631.I55790-100000@megazone.bigpanda.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox