Skip site navigation (1) Skip section navigation (2)

Re: Problem with pg_dumpall

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ryan Bradetich <ryan_bradetich(at)hp(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Problem with pg_dumpall
Date: 2000-06-27 22:02:01
Message-ID: 16833.962143321@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-sql
Ryan Bradetich <ryan_bradetich(at)hp(dot)com> writes:
> Tom Lane wrote:
>> Ryan Bradetich <ryan_bradetich(at)hp(dot)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

In response to

Responses

pgsql-sql by date

Next:From: Ryan BradetichDate: 2000-06-27 23:14:35
Subject: Re: Problem with pg_dumpall
Previous:From: Ryan BradetichDate: 2000-06-27 21:55:06
Subject: Re: Problem with pg_dumpall

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group