Problem with pg_dumpall in reverse

Ok- this may be a simple answer, but-

Once the database has been dumped, how do you restore while keeping the original OIDs? I've used the OID as a unique key that ties records together, and somehow they don't go back together nicely...

doing a dump with "pg_dumpall -o -c > db.out"
restoring with "cat db.out | psql"

Thanks,
Kenn

>>> Ryan Bradetich <ryan_bradetich(at)hp(dot)com> 06/27/00 11:27AM >>>
Hello all,

I am having a new problem with pg_dumpall that I have not seen before.
I've been
browsing the documentation and could not find anything related to this
problem. Any
ideas or pointers would greatly be appreciated.

boi260 sanity $ /opt/pgsql/bin/pg_dumpall -v -o | /usr/contrib/bin/gzip
-c > /opt/pgsql/backup/db.pgdump.gz

[ Extra verbage snipped ]

-- dumping out the contents of Table 'medusa'
FATAL 1: Memory exhausted in AllocSetAlloc()
PQendcopy: resetting connection
SQL query to dump the contents of Table 'medusa' did not execute
correctly. After we read all the table contents from the backend,
PQendcopy() failed. Explanation from backend: 'FATAL 1: Memory
exhausted in AllocSetAlloc()
'.
The query was: 'COPY "medusa" WITH OIDS TO stdout;
'.
pg_dump failed on procman, exiting

procman=# select version();
version
-------------------------------------------------------------------
PostgreSQL 7.0.0 on hppa2.0w-hp-hpux11.00, compiled by gcc 2.95.2
(1 row)

Thanks,

- Ryan