Hi,

I get the following error when I call:

# pg_dump db
pg_dump: schema with OID 559701082 does not exist

this happens with 8.0.1 on RHEL 3.0. I cannot dump the database neither
with --schema-only or --data-only.

What can I do?

Thanks for help,

Dirk

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

=?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= <lutzeb (AT) aeccom (DOT) com> writes:
I suspect a corrupted catalog entry. Look through your system catalogs
for an entry referring to namespace 559701082 --- you want to look in
pg_class.relnamespace, pg_proc.pronamespace, etc.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

=?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= <lutzeb (AT) aeccom (DOT) com> writes:
Uh, are you sure these are in a schema that's in your search path?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

Yes, I think so. What search path do you mean? These tables were all
temporary tables.

Dirk


Tom Lane wrote:

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

=?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= <lutzeb (AT) aeccom (DOT) com> writes:
In that case they're most likely *not* in your search path, unless your
session happens to have seized on the same pg_temp_nn schema they are
in (in which case it'd have deleted them, so I guess it didn't).

I'd suggest joining to pg_namespace to determine which schema(s) they
are in, and then deleting with the explicit schema, ie, DROP TABLE
pg_temp_nnn.bm_pagehits_... Note you'll probably need to be superuser
to do this.

Or you could just ignore them, because they'll get zapped automatically
next time the containing pg_temp schema gets reused.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

I have found and deleted an entry with pg_class.relnamespace=559701082
but nowhere else. I still cannot dump the schema. Is there something
like a system catalog integrity checker?

The problem I'm facing is the following:

cs1=# select relname from pg_class where relname like 'bm%';
relname
-----------------------------------
bm_pagehits_1133271374_047421_941
bm_pagehits_1133271378_920896_129
bm_pagehits_1133282272_744243_536
bm_pagehits_1133284780_743839_884
(4 rows)

cs1=# drop table bm_pagehits_1133271374_047421_941;
ERROR: table "bm_pagehits_1133271374_047421_941" does not exist
cs1=# drop table bm_pagehits_1133271378_920896_129;
ERROR: table "bm_pagehits_1133271378_920896_129" does not exist
cs1=# drop table bm_pagehits_1133282272_744243_536;
ERROR: table "bm_pagehits_1133282272_744243_536" does not exist
cs1=# drop table bm_pagehits_1133284780_743839_884;
ERROR: table "bm_pagehits_1133284780_743839_884" does not exist





Tom Lane wrote:

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

=?ISO-8859-1?Q?Dirk_Lutzeb=E4ck?= <lutzeb (AT) aeccom (DOT) com> writes:
Better keep looking then. See
http://www.postgresql.org/docs/8.1/static/catalogs.html
(adjust link for your PG version) to find out which catalogs reference
pg_namespace.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Yes, I finally found the reference in pg_type.

Thanks for your help!

Regards,

Dirk


Tom Lane wrote:

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster