Re: ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephane Bailliez <sbailliez(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table
Date: 2007-11-12 22:54:22
Message-ID: 13448.1194908062@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Stephane Bailliez <sbailliez(at)gmail(dot)com> writes:
> ERROR: invalid memory alloc request size 1664639562

This sounds like corrupt data --- specifically, 1664639562 showing
up where a variable-width field's length word ought to be. It
may or may not be relevant that the ASCII equivalent of that bit
pattern is Jb8c ... do you work with data that contains such
substrings?

> Sometimes I do get:
> ERROR: unexpected end of data

If it's not 100% repeatable I'd start to wonder about flaky hardware.
Have you run memory and disk diagnostics on this machine recently?

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Rafael Martinez 2007-11-13 08:49:43 Re: Need to run CLUSTER to keep performance
Previous Message Stephane Bailliez 2007-11-12 19:57:48 ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table