Received: from cosrel2.hp.com (cosrel2.hp.com [156.153.255.162]) by hub.org (8.10.1/8.10.1) with ESMTP id e5RNEf148646 for ; Tue, 27 Jun 2000 19:14:41 -0400 (EDT) Received: from hpbs5000.boi.hp.com (hpbs5000.boi.hp.com [15.56.8.201]) by cosrel2.hp.com (Postfix) with ESMTP id 0D28827E; Tue, 27 Jun 2000 17:14:36 -0600 (MDT) 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 RAA00798; Tue, 27 Jun 2000 17:14:35 -0600 (MDT) Message-ID: <3959355B.762D586C@hp.com> Date: Tue, 27 Jun 2000 17:14:35 -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> <395922BA.2F477593@hp.com> <16833.962143321@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200006/246 Tom Lane wrote: > Ryan Bradetich writes: > > 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; > > Now that I look at it, it appears that COPY WITH OIDS leaks the memory > used for the string representation of the OIDs. That'd probably cost > you 32 bytes or so of backend memory per row --- which you'd get back > at the end of the COPY, but small comfort if you ran out before that. > > Is the table large enough to make that a plausible explanation? > > regards, tom lane Tom, This table is very large so that could be the problem. Here are the startup parameters I am using (in case it matters): -B 1024 -S -o -F -o -o /home/postgres/nohup.out -i -p 5432 -D/data08 nohup su - postgres -c "/opt/pgsql/bin/postmaster -B 1024 -S -o \"-F\" -o \"-o /home/postgres/nohup.out\" -i -p 5432 -D/data08" procman=# select count(*) from medusa; count --------- 6986499 (1 row) FYI: That was the problem. Good job at spotting that Tom. I just successfully completed a backup without using the -o option to pg_dumpall. Thanks again for the help! - Ryan -- Ryan Bradetich AIT Operations Unix Platform Team