pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ryan Bradetich <ryan_bradetich@hp.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Problem with pg_dumpall
Date: Tue, 27 Jun 2000 18:02:01 -0400
Message-ID: <16833.962143321@sss.pgh.pa.us> (raw)
In-Reply-To: <395922BA.2F477593@hp.com>
References: <3958D5EA.82E74C68@hp.com>
	<14979.962142613@sss.pgh.pa.us>
	<395922BA.2F477593@hp.com>

Ryan Bradetich <ryan_bradetich@hp.com> writes:
> Tom Lane wrote:
>> Ryan Bradetich <ryan_bradetich@hp.com> 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



view thread (6+ messages)  latest in thread

Message-ID: <16833.962143321@sss.pgh.pa.us>
Permalink:  ../16833.962143321@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/16833.962143321@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, ryan_bradetich@hp.com
  Subject: Re: Problem with pg_dumpall
  In-Reply-To: <16833.962143321@sss.pgh.pa.us>
  References: <3958D5EA.82E74C68@hp.com> <14979.962142613@sss.pgh.pa.us> <395922BA.2F477593@hp.com> <16833.962143321@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox