Re: pg_dump fail beacuse of oid larger than int32

>From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
>To: "Ragnar Garli" <ragnar_garli(at)hotmail(dot)com>
>CC: pgsql-general(at)postgresql(dot)org
>Subject: Re: [GENERAL] pg_dump fail beacuse of oid larger than int32 Date:
>Tue, 14 Jan 2003 10:50:03 -0500
>
>"Ragnar Garli" <ragnar_garli(at)hotmail(dot)com> writes:
> > I have a problem with pg_dump du to oid values larger than signed 32 bit
> > int.
>
>Use a more recent pg_dump. 7.3.1's pg_dump should be able to talk to
>your 7.1.3 server and extract the data without problems.
>
> regards, tom lane
Sorry, but pg_dump from 7.3.1 fails too. The problem is the errormessage it
gets from the backend when pg_dump scans throug the pg_description table
using the oids for the tables in the database.

Just look at the d2 debug output from the postmaster:
DEBUG: StartTransactionCommand
DEBUG: query: SELECT description FROM pg_description WHERE objoid =
2325712020
ERROR: dtoi4: integer out of range
DEBUG: AbortCurrentTransaction

when this comes throug pg_dump it looks like:
postgres(at)bravo4:~/7_3_1_binaries$ pg_dumpall >outfile
DumpComment: SELECT failed: 'ERROR: dtoi4: integer too large
'.
pg_dump failed on combi00001, exiting

The original error message was "integer out of range", but somwhere along
the way, somebody advised me to split the test in too small and too large.

Regards:
Ragnar Garli

_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail