From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephane Bailliez <sbailliez@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table
Date: Mon, 12 Nov 2007 17:54:22 -0500
Message-ID: <13448.1194908062@sss.pgh.pa.us> (raw)
In-Reply-To: <4738B03C.8090901@gmail.com>
References: <4738B03C.8090901@gmail.com>
Stephane Bailliez <sbailliez@gmail.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, sbailliez@gmail.com
Subject: Re: ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table
In-Reply-To: <13448.1194908062@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox