Re: AllocSetAlloc() error message

From: Medi Montaseri <medi(dot)montaseri(at)intransa(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: AllocSetAlloc() error message
Date: 2003-02-07 05:31:28
Message-ID: 3E4344B0.4010307@intransa.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Should I be looking for an exsessively large table or column ?
Most (99%) of my tables are text fields, but small values (less than
1024 bytes)....
Perhaps I should dump the data and go after it with a perl script....

Also this happend around a VACUUM-ing job....is there any relation there ?
Also should I drop my other work and chase this or this is more of
warning than an error....

Thanks

Tom Lane wrote:

>Medi Montaseri <medi(dot)montaseri(at)intransa(dot)com> writes:
>
>
>>Can someone shed some light on this error message for me (please).
>>This is a 7.2.3 debug level 2 output, and my config is
>>
>>
>
>
>
>>2003-02-06 16:15:44 [645] ERROR: Memory exhausted in
>>AllocSetAlloc(1073741820)
>>
>>
>
>I think this is a corrupt-data problem: you've probably got a
>variable-length datum whose length word is munged to look like a
>ridicuously large value. You should be scanning the table to see
>where the bad data is.
>
> regards, tom lane
>
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Shridhar Daithankar 2003-02-07 06:37:23 Re: Pg_dumpall problem[2]
Previous Message John Smith 2003-02-07 05:01:14 selects with large offset really slow