Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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

pgsql-performance by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group