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 e5RM29193381 for ; Tue, 27 Jun 2000 18:02:09 -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 SAA16836; Tue, 27 Jun 2000 18:02:01 -0400 (EDT) To: Ryan Bradetich cc: pgsql-sql@postgresql.org Subject: Re: Problem with pg_dumpall In-reply-to: <395922BA.2F477593@hp.com> References: <3958D5EA.82E74C68@hp.com> <14979.962142613@sss.pgh.pa.us> <395922BA.2F477593@hp.com> Comments: In-reply-to Ryan Bradetich message dated "Tue, 27 Jun 2000 15:55:06 -0600" Date: Tue, 27 Jun 2000 18:02:01 -0400 Message-ID: <16833.962143321@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200006/245 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