RE: Table Drop Error
От | |
---|---|
Тема | RE: Table Drop Error |
Дата | |
Msg-id | 2A91BEF8171A5349931391E0C721CC531D6DBD3F@CPEMS-KPN301.KPNCNL.LOCAL обсуждение исходный текст |
Ответ на | Re: Table Drop Error (Laurenz Albe <laurenz.albe@cybertec.at>) |
Ответы |
Re: Table Drop Error
|
Список | pgsql-admin |
But what is the solution in this case? -----Original Message----- From: Laurenz Albe <laurenz.albe@cybertec.at> Sent: Sunday, February 17, 2019 8:35 PM To: Bhattacharjee, Soumik <soumik.bhattacharjee@kpn.com>; tgl@sss.pgh.pa.us Cc: pgsql-admin@lists.postgresql.org Subject: Re: Table Drop Error soumik.bhattacharjee@kpn.com wrote: > From: Tom Lane <tgl@sss.pgh.pa.us> > > <soumik.bhattacharjee@kpn.com> writes: > > > # delete from pg_depend where objid=49179; DELETE 0 # delete from > > > pg_depend where objid=49179; DELETE 0 # DROP TABLE > > > caprimeta.tcr_codes CASCADE; > > > ERROR: cache lookup failed for relation 49179 > > > > It's not really a great idea to go dropping catalog rows without knowing exactly what you're doing, which I gather youdon't. > > However ... are there pg_depend entries with refobjid=49179 ? > > Thanks for the mail, there is no entries in pg_depend as it returns " DELETE 0" > But the table is not getting dropped. Please read again. "refobjid=49179", not "objid=49179". Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com
В списке pgsql-admin по дате отправления: