Re: Invalid memory alloc request - Mailing list pgsql-general

From Tom Lane
Subject Re: Invalid memory alloc request
Date
Msg-id 22530.1251217440@sss.pgh.pa.us
Whole thread Raw
In response to Re: Invalid memory alloc request  (Guy Helmer <ghelmer@palisadesys.com>)
Responses Re: Invalid memory alloc request
List pgsql-general
Guy Helmer <ghelmer@palisadesys.com> writes:
> Tom Lane wrote:
>> Normally I'd say "data corruption", but it is odd if you got the
>> identical message from two different machines.  Can you reproduce
>> it with a debugger attached?  If so, a backtrace from the call of
>> errfinish might be useful.

> Yes, here is the backtrace.

Well, that looks just about like you'd expect for a bytea column.

Hmm ... you mentioned 500MB total in the textdata column.  Is it
possible that that's nearly all in one entry?  It's conceivable
that the text representation of the entry is simply too large.
(The next question of course would be how you got the entry in there,
but maybe it was submitted in binary protocol, or built by
concatenation.)

            regards, tom lane

pgsql-general by date:

Previous
From: Sébastien Lardière
Date:
Subject: WAL Shipping + checkpoint
Next
From: Martin Gainty
Date:
Subject: Re: ETL software and training