Re: Error on pg_dumpall - Mailing list pgsql-admin

From Terry Khatri
Subject Re: Error on pg_dumpall
Date
Msg-id CANH4f+iOF-8tQp-7=H9Upm89GmT4JreNS8SV=wTz3hxj7zpofA@mail.gmail.com
Whole thread Raw
In response to Re: Error on pg_dumpall  (Craig Ringer <ringerc@ringerc.id.au>)
List pgsql-admin


On 23 October 2012 10:15, Craig Ringer <ringerc@ringerc.id.au> wrote:

First, try per-database dumps. Work out which database has the problem.
Do a:

    pg_dumpall -U sns84  --globals-only > globals.sql

then for each database:

    pg_dump -U sns84 -f $dbname.sql $dbname
 

(scripting it if desired), until you see which DB fails to dump. Dump
all the DBs you can successfully dump before proceeding.
 
Then, in the problem dB, try:

    REINDEX pg_catalog.pg_namespace;

does that help?
Nope, same problem still - I knew already which db is failing pls see my initial msg

pg_dump: schema with OID 74363 does not exist

 
 
What's the output of:

    SELECT oid, nspname FROM pg_catalog.pg_namespace;

in the problem DB?

nspname

---------

99

11194

11195

11

2200

11459

82537

(7 rows)

 
That oid does'nt show up here !
 

List of schemas

Name       | Owner

-------------+---------

public       | sns84

 bihistory  | sns84

(2 rows)


Is all your data for the problem DB in the "public" schema? If so, can
you do a schema-only dump?

  pg_dump -U sns84 -n public -f $dbname.dump $dbname
 No it is in its own schema i.e. bihistory
 
Please let me know if there's any tweaking that we do in the catalog to fix it.
Thank you very much for your help
Rgds
T



pgsql-admin by date:

Previous
From: teyking2003
Date:
Subject: Re: Database in psql
Next
From: teyking2003
Date:
Subject: Re: Auto Vacuum