RE: Table Drop Error

From: <soumik(dot)bhattacharjee(at)kpn(dot)com>
To: <laurenz(dot)albe(at)cybertec(dot)at>, <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-18 09:01:10
Message-ID: 2A91BEF8171A5349931391E0C721CC531D6DBD3F@CPEMS-KPN301.KPNCNL.LOCAL
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

But what is the solution in this case?

-----Original Message-----
From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Sent: Sunday, February 17, 2019 8:35 PM
To: Bhattacharjee, Soumik <soumik(dot)bhattacharjee(at)kpn(dot)com>; tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Table Drop Error

soumik(dot)bhattacharjee(at)kpn(dot)com wrote:
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> > <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 ?
>
> 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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Mariel Cherkassky 2019-02-18 14:15:02 repmgr standby clone fails
Previous Message Mariel Cherkassky 2019-02-17 21:58:23 Re: pg_restore fails to restore sequence of specific table