pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kenn Thompson <KThompson@adestagroup.com>
To: pgsql-sql@postgresql.org
Subject: Problem with pg_dumpall in reverse
Date: Tue, 27 Jun 2000 13:10:18 -0500
Message-ID: <s958a7cc.064@10.0.0.4> (raw)

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@hp.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






Message-ID: <s958a7cc.064@10.0.0.4>
Permalink:  ../s958a7cc.064@10.0.0.4/
Also on:    postgresql.org/message-id/s958a7cc.064@10.0.0.4

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: KThompson@adestagroup.com
  Subject: Re: Problem with pg_dumpall in reverse
  In-Reply-To: <s958a7cc.064@10.0.0.4>
  References: <s958a7cc.064@10.0.0.4>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox