Received: from atlrel1.hp.com (atlrel1.hp.com [156.153.255.210]) by hub.org (8.10.1/8.10.1) with ESMTP id e5RGRO105471 for ; Tue, 27 Jun 2000 12:27:24 -0400 (EDT) Received: from hpbs5000.boi.hp.com (hpbs5000.boi.hp.com [15.56.8.201]) by atlrel1.hp.com (Postfix) with ESMTP id 0D0151A950 for ; Tue, 27 Jun 2000 12:27:23 -0400 (EDT) Received: from hp.com (rbrad@hpb50023.boise.itc.hp.com [15.62.176.50]) by hpbs5000.boi.hp.com with ESMTP (8.8.6 (PHNE_17135)/8.8.6 SMKit7.02) id KAA10549 for ; Tue, 27 Jun 2000 10:27:22 -0600 (MDT) Message-ID: <3958D5EA.82E74C68@hp.com> Date: Tue, 27 Jun 2000 10:27:22 -0600 From: Ryan Bradetich X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.3.99-pre3 i686) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: Problem with pg_dumpall Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200006/242 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