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

From: "Reid Thompson" <Reid(dot)Thompson(at)ateb(dot)com>
To:
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_dump: ERROR: Memory exhausted in AllocSetAlloc(875574064)
Date: 2005-05-12 19:17:52
Message-ID: F71C0DC6B4FD3648815AAA7F969E3529F49221@sr002-2kexc.ateb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> "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

No, no 875MB fields -- the largest field is limited to 2048 chars.
Heading to the archives.

thanks,

reid

Browse pgsql-general by date

  From Date Subject
Next Message Havasvölgyi Ottó 2005-05-12 19:34:46 Re: About Types
Previous Message Ralf Schuchardt 2005-05-12 19:12:35 Re: Delphi 2005, Postgresql, ZEOS & optimistic locking