From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | 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 |
Date: | 2019-02-17 19:34:40 |
Message-ID: | 10223d001b83afa185f5ec689b0cc6591c3fa15f.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Mariel Cherkassky | 2019-02-17 20:29:21 | Re: pg_restore fails to restore sequence of specific table |
Previous Message | Laurenz Albe | 2019-02-17 19:31:14 | Re: pg_restore fails to restore sequence of specific table |