From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Reid Thompson <Reid(dot)Thompson(at)ateb(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump: ERROR: Memory exhausted in AllocSetAlloc(875574064) |
Date: | 2005-05-13 01:46:22 |
Message-ID: | 20050513014616.GD29735@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, May 12, 2005 at 02:56:35PM -0400, 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.
Just for curiosity sake:
875574064 base 10 = 34303330 base 16
Looks like the ASCII string "4030"
Definitly corrupted tuple...
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a
> tool for doing 5% of the work and then sitting around waiting for someone
> else to do the other 95% so you can sue them.
From | Date | Subject | |
---|---|---|---|
Next Message | Aly Dharshi | 2005-05-13 02:25:11 | Postgres 8.0.3 Fedora RPMS ? |
Previous Message | Ned Lilly | 2005-05-13 00:26:03 | Re: Please Recommend a Front End App |