From: Laurenz Albe <laurenz.albe@cybertec.at>
To: soumik.bhattacharjee@kpn.com
To: tgl@sss.pgh.pa.us
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Table Drop Error
Date: Sun, 17 Feb 2019 20:34:40 +0100
Message-ID: <10223d001b83afa185f5ec689b0cc6591c3fa15f.camel@cybertec.at> (raw)
In-Reply-To: <2A91BEF8171A5349931391E0C721CC531D6DB96D@CPEMS-KPN301.KPNCNL.LOCAL>
References: <2A91BEF8171A5349931391E0C721CC531D6DB881@CPEMS-KPN301.KPNCNL.LOCAL>
<3681.1550246571@sss.pgh.pa.us>
<2A91BEF8171A5349931391E0C721CC531D6DB96D@CPEMS-KPN301.KPNCNL.LOCAL>
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 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, soumik.bhattacharjee@kpn.com, tgl@sss.pgh.pa.us, pgsql-admin@lists.postgresql.org
Subject: Re: Table Drop Error
In-Reply-To: <10223d001b83afa185f5ec689b0cc6591c3fa15f.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox