Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e5RLoP165274 for ; Tue, 27 Jun 2000 17:50:26 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id RAA14982; Tue, 27 Jun 2000 17:50:13 -0400 (EDT) To: Ryan Bradetich cc: pgsql-sql@postgresql.org Subject: Re: Problem with pg_dumpall In-reply-to: <3958D5EA.82E74C68@hp.com> References: <3958D5EA.82E74C68@hp.com> Comments: In-reply-to Ryan Bradetich message dated "Tue, 27 Jun 2000 10:27:22 -0600" Date: Tue, 27 Jun 2000 17:50:13 -0400 Message-ID: <14979.962142613@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200006/243 Ryan Bradetich writes: > -- 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; Hmm. What is the full definition of that table? (pg_dump -s -t medusa would do.) regards, tom lane