Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Mon, 12 Nov 2007 17:54:22 -0500
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
- Follow-Ups:
- Re: ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table
- From: Stephane Bailliez
- Re: ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table
- References:
- ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table
- From: Stephane Bailliez
- ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table
- Prev by Date: ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table
- Next by Date: Re: Need to run CLUSTER to keep performance
- Previous by thread: ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table
- Next by thread: Re: ERROR: "invalid memory alloc request size" or "unexpected end of data" on large table
- Indexes: