Thread: integer out of range errors

Howdy:

Running PostgreSQL 7.1.3 on RedHat Linux 7.2 kernel 2.4.7-10.

We are having some problems trying to figure out what is causing
the following errors (and, if they are effecting something else).

When I do a pg_dump, I get the following:

[snip error]
getTables(): SELECT (for PRIMARY KEY) failed on table t_prof_er_full_detail.  Explanation from backend: ERROR:  dtoi4: integer out of range

[/snip error]

I've read around and a few articles in the google newsgroup says to
get pg_dump 7.2 (which suppose to dump for PostgreSQL 7.1 as well)
and if that is so, then:

a) where do I find pg_dump 7.2 (as a source code or a binary somewhere?)
b) how does this effect other things like pgAdmin II (where I get a similar
error regarding a key (if it's related at all! *shrug*)
c) does OID max out at 2 billion before i start to get errors?

Not sure about a lot of this (as I'm still learning = breaking things).
Any suggestions would be appreciated.

Thanks!

-X

"Johnson, Shaunn" <SJohnson6@bcbsm.com> writes:
> When I do a pg_dump, I get the following:

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

How long has your installation been running?  I'm guessing that this is
a problem with OIDs > 2 billion (causing signed vs unsigned problems),
but that doesn't hold water unless you've been running long enough to
have such OIDs.

> I've read around and a few articles in the google newsgroup says to
> get pg_dump 7.2 (which suppose to dump for PostgreSQL 7.1 as well)

That'd be my recommendation too: get 7.2, build it, use the pg_dump
from it to dump everything, then install 7.2 and reload the dump.

> b) how does this effect other things like pgAdmin II

Anything that's careless about whether OIDs are signed or unsigned
will have problems.  We've flushed most such bugs out of pg_dump by
now, but I dunno about pgadmin.

            regards, tom lane