Re: Unable to drop a table due to seemingly non-existent dependencies

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: Unable to drop a table due to seemingly non-existent dependencies
Дата
Msg-id
6400.1252608918@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
Unable to drop a table due to seemingly non-existent dependencies David Brain <dbrain@bandwidth.com>
Re: Unable to drop a table due to seemingly non-existent dependencies Richard Huxton <dev@archonet.com>
Re: Unable to drop a table due to seemingly non-existent dependencies Tom Lane <tgl@sss.pgh.pa.us>
Re: Unable to drop a table due to seemingly non-existent dependencies David Brain <dbrain@bandwidth.com>
David Brain  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 по дате отправления
От: Richard Huxton
Дата:
От: Tom Lane
Дата:
FAQ