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.montaseri@intransa.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
>
>
