Re: pg_dump: ERROR: Memory exhausted in AllocSetAlloc(875574064)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Reid Thompson" <Reid(dot)Thompson(at)ateb(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dump: ERROR: Memory exhausted in AllocSetAlloc(875574064)
Date: 2005-05-12 18:56:35
Message-ID: 11362.1115924195@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Reid Thompson" <Reid(dot)Thompson(at)ateb(dot)com> writes:
> Is there any solution to this other than adding memory, or am I
> mis-understanding the error?

> pg_dump: ERROR: Memory exhausted in AllocSetAlloc(875574064)
> pg_dump: lost synchronization with server, resetting connection

My bet is that this is actually a corrupt-data problem ... unless you
actually have any 875MB fields in your table. The implication is that
the length word of a variable-width field contains garbage. More than
likely, the whole tuple is garbaged, but this happens to be the first
visible symptom.

There is plenty of discussion of recovering from data corruption in
the archives, so go have a look.

> v7.2.3 on RHAT 7.3 linux with 128MB RAM.

Might want to think about an update sometime, too ;-)

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jimmie H. Apsey 2005-05-12 19:00:50 Re: pg_dump fails on 7.4 Postgres
Previous Message mmiranda 2005-05-12 18:42:24 Re: About Types