From: | Peter Neish <peter(at)austehc(dot)unimelb(dot)edu(dot)au> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_dump: schema with OID xxxxxxxx does not exist |
Date: | 2006-11-01 23:33:53 |
Message-ID: | 45492EE1.2080706@austehc.unimelb.edu.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
>
>> Yes, 32 entries.
>>
>
> Wow, that's the first case I've heard of where whole tables were left
> around with no matching schema. You'll probably find you have to drop
> both the pg_class and pg_type rows before pg_dump will work --- AFAIR
> you shouldn't have to clean out pg_attribute.
>
>
Thanks Tom. I was able to run pg_dump successfully after clearing those
rows from the pg_class and pg_type tables.
> Since it's hard to tell exactly what's going on here, I'd suggest a
> pg_dumpall/initdb/reload sequence to be sure there isn't any other
> undetected corruption. Be sure to check that the dump contains
> everything you expect though.
>
Will do this. Sounds like there's some hairy stuff going on and a good
cleanout would be a good idea (as well as a PG upgrade).
Thanks again for your help.
Peter
From | Date | Subject | |
---|---|---|---|
Next Message | Shoaib Mir | 2006-11-02 07:44:38 | Re: New to PostgreSQL |
Previous Message | Mark Steben | 2006-11-01 19:39:09 | New to PostgreSQL |