Re: Unable to drop a table due to seemingly non-existent dependencies - Mailing list pgsql-general

From Tom Lane
Subject Re: Unable to drop a table due to seemingly non-existent dependencies
Date
Msg-id 6400.1252608918@sss.pgh.pa.us
Whole thread Raw
In response to Unable to drop a table due to seemingly non-existent dependencies  (David Brain <dbrain@bandwidth.com>)
Responses Re: Unable to drop a table due to seemingly non-existent dependencies  (David Brain <dbrain@bandwidth.com>)
List pgsql-general
David Brain <dbrain@bandwidth.com> writes:
> I have a situation where trying to drop a table results in:

> #drop table cdrimporterror_old;
> NOTICE:  default for table cdrimporterror column cdrimporterrorid
> depends on sequence cdrimporterror_cdrimporterrorid_seq
> ERROR:  cannot drop table cdrimporterror_old because other objects depend on it
> HINT:  Use DROP ... CASCADE to drop the dependent objects too.

> Now as you can probably imply from the name if this table, this table
> has been renamed from cdrimporterror to cdrimporterorr_old and I have
> (or at least thought I had) removed it's dependency on the sequence by
> changing the tables column type (from bigserial to bingint) and
> removing the default value.

The "ownership" link is still there, evidently, and should be switched
to the new table.  Read up on ALTER SEQUENCE OWNED BY.

            regards, tom lane

pgsql-general by date:

Previous
From: Richard Huxton
Date:
Subject: Re: Unable to drop a table due to seemingly non-existent dependencies
Next
From: Tom Lane
Date:
Subject: Re: Getting the oid of an anyelement