RE: Table Drop Error

From: <soumik(dot)bhattacharjee(at)kpn(dot)com>
To: <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: RE: Table Drop Error
Date: 2019-02-15 16:22:25
Message-ID: 2A91BEF8171A5349931391E0C721CC531D6DB96D@CPEMS-KPN301.KPNCNL.LOCAL
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi Tom,

Thanks for the mail, there is no entries in pg_depend as it returns " DELETE 0"

But the table is not getting dropped.

Thanks

-----Original Message-----
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Sent: Friday, February 15, 2019 5:03 PM
To: Bhattacharjee, Soumik <soumik(dot)bhattacharjee(at)kpn(dot)com>
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Table Drop Error

<soumik(dot)bhattacharjee(at)kpn(dot)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 you don't.
However ... are there pg_depend entries with refobjid=49179 ?

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Mariel Cherkassky 2019-02-17 12:03:26 pg_restore fails to restore sequence of specific table
Previous Message Tom Lane 2019-02-15 16:02:51 Re: Table Drop Error