From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Terry Khatri <terrykhatri531(at)gmail(dot)com> |
Cc: | Lukasz Brodziak <lukasz(dot)brodziak(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Fwd: Errors on pg_dumpall |
Date: | 2012-11-05 15:22:37 |
Message-ID: | 27171.1352128957@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Terry Khatri <terrykhatri531(at)gmail(dot)com> writes:
> Okay, I have found a reference to that oid in pg_type as under :
> select * from pg_type where typnamespace=74363 ;
Okay, so you have a composite type named "city" (either a table's
rowtype, or a standalone composite type --- hard to tell from just this
entry) that somehow escaped deletion when the containing schema was
deleted. Do you have an idea what triggered that? A reproducible test
case would be even better.
> What I should do next ?
Well, you can just manually delete those rows in pg_type, if you're sure
that there's nothing else linking to them. It might be safer to try to
do it as "drop type city" first.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Terry Khatri | 2012-11-05 19:36:22 | Re: Cannot take base backup of a master database |
Previous Message | Cédric Villemain | 2012-11-05 15:12:42 | Re: Autoanalyze of the autovacuum daemon ... |