Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.org (8.10.1/8.10.1) with ESMTP id e5RLt8178469 for ; Tue, 27 Jun 2000 17:55:08 -0400 (EDT) Received: from hpbs5000.boi.hp.com (hpbs5000.boi.hp.com [15.56.8.201]) by palrel1.hp.com (Postfix) with ESMTP id B918AB92; Tue, 27 Jun 2000 14:55:06 -0700 (PDT) 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 PAA22046; Tue, 27 Jun 2000 15:55:06 -0600 (MDT) Message-ID: <395922BA.2F477593@hp.com> Date: Tue, 27 Jun 2000 15:55:06 -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: Tom Lane Cc: pgsql-sql@postgresql.org Subject: Re: Problem with pg_dumpall References: <3958D5EA.82E74C68@hp.com> <14979.962142613@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200006/244 Tom Lane wrote: > 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 Tom, boi260 /data08 $ pg_dump -s -t medusa procman \connect - postgres CREATE TABLE "medusa" ( "host_id" int4, "timestamp" timestamp, "current" int4, "catagory" text, "cat_desc" text, "anomaly" text ); CREATE INDEX "medusa_catagory_key" on "medusa" using btree ( "catagory" "text_ops" ); CREATE INDEX "medusa_host_id_key" on "medusa" using btree ( "host_id" "int4_ops" ); CREATE INDEX "medusa_current_key" on "medusa" using btree ( "current" "int4_ops" ); Ryan