Re: Invalid memory alloc request

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Guy Helmer <ghelmer(at)palisadesys(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Invalid memory alloc request
Date: 2009-08-25 16:24:00
Message-ID: 22530.1251217440@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Guy Helmer <ghelmer(at)palisadesys(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martin Gainty 2009-08-25 16:27:50 Re: ETL software and training
Previous Message Marcus Engene 2009-08-25 16:16:51 somewhat slow query with subselect