From: | Ryan Bradetich <ryan_bradetich(at)hp(dot)com> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Problem with pg_dumpall |
Date: | 2000-06-27 16:27:22 |
Message-ID: | 3958D5EA.82E74C68@hp.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Kenn Thompson | 2000-06-27 18:10:18 | Problem with pg_dumpall in reverse |
Previous Message | Saltsgaver, Scott | 2000-06-27 16:17:20 | Creating tables from within functions |