Pg_dump and huge OID's

From: "Glen Parker" <glenebob(at)nwlink(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Pg_dump and huge OID's
Date: 2002-05-24 01:17:18
Message-ID: 006a01c202c0$bf3bf830$0b01a8c0@johnpark.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Somehow I've gotten OID's > 2147483647 in my database. I have yet to
figure out how that could have happened, since I just did a restore a
few days ago and I'm not recording OID's in the dumps. Any suggestions
how this might happen would be appreciated.

The real problem though is why I can't do a pg_dump now. I get this
error from pg_dump:

getTables(): SELECT (for PRIMARY KEY) failed on table itemadj.
Explanation from backend: ERROR: dtoi4: integer out of range

The indexes on this table have very large OID's. They are valid as
OID's, but not as INT4's, so apparently pg_dump doesn't do a proper cast
when querying the pg_class table?

Any suggestions how to fix this or get a dump? This is quickly getting
scarey, since I can't see a way to get a backup. Bad bad bad.

Btw, this is postgres 7.1.3 (select version() says:)
PostgreSQL 7.1.3 on i686-pc-linux-gnu, compiled by GCC 2.96

Running on Redhat 7.2.

Thx in advance,

Glen Parker
glenebob(at)nwlink(dot)com

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alan Wayne 2002-05-24 03:57:25 Help with "empty()"
Previous Message Nigel J. Andrews 2002-05-23 23:41:30 Re: Process balancing on smp db server/apache web serve