From: Bret Hughes <bhughes@elevating.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: postgresql sql list <pgsql-sql@postgresql.org>
Subject: Re: trigger/for key help
Date: 11 Apr 2004 17:58:37 -0500
Message-ID: <1081724318.2628.20.camel@bretsony> (raw)
In-Reply-To: <17189.1081720813@sss.pgh.pa.us>
References: <1081662204.6609.72.camel@bretsony>
<20040411080932.Q83278@megazone.bigpanda.com>
<1081711155.6399.165.camel@bretsony>
<17189.1081720813@sss.pgh.pa.us>
On Sun, 2004-04-11 at 17:00, Tom Lane wrote:
> Bret Hughes <bhughes@elevating.com> writes:
> > elevating=# drop table test_types;
> > ERROR: could not find tuple for constraint 2041971
>
> > I can find no reference to these oids anywhere.
>
> You haven't looked very hard then ;-). I expect this is because
> pg_depend has links from the table to the constraints it owns.
> You could probably remove the pg_depend entries to make it possible
> to drop the table.
>
> Use ALTER TABLE next time, eh? Hand manipulation of the system catalogs
> is *not* for those who don't know exactly what they are doing.
>
> regards, tom lane
Hmm I thought I had but pg_depend is one that I missed. I deleted all
refs to rows in pg_depends and was able to drop the table.
FWIW I tried to use alter table but could never get the parser to accept
$1 as a constraint name. I used single and double quotes as well as a
lame attempt \$1.
Thanks I am breathing better. I was about to pg_dump and restore into a
test database to see what would happen then since there was no reference
to any of the oids in the error messages found in the dump.
I can now resume climbing up the learning curve.
Bret
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: bhughes@elevating.com, tgl@sss.pgh.pa.us, sszabo@megazone.bigpanda.com
Subject: Re: trigger/for key help
In-Reply-To: <1081724318.2628.20.camel@bretsony>
* 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