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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: ERROR: invalid memory alloc request size <a_big_number_here>


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: Matteo Beccati <php(at)beccati(dot)com>
  • Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: ERROR: invalid memory alloc request size <a_big_number_here>
  • Date: Thu, 27 Oct 2005 09:40:02 -0400
  • Message-id: <18237(dot)1130420402(at)sss(dot)pgh(dot)pa(dot)us>

Matteo Beccati <php(at)beccati(dot)com> writes:
> (gdb) bt
> #0  errfinish (dummy=0) at elog.c:346
> #1  0x08265896 in elog_finish (elevel=20, fmt=0x831858c "invalid memory 
> alloc request size %lu") at elog.c:930
> #2  0x0827b5cf in MemoryContextAlloc (context=0x85b2238, 
> size=4279476584) at mcxt.c:505
> #3  0x080b6a16 in GetMultiXactIdMembers (multi=301994, xids=0xbfbfaba4) 
> at multixact.c:935
> #4  0x080b6271 in MultiXactIdIsRunning (multi=301994) at multixact.c:373
> #5  0x0828347d in HeapTupleSatisfiesUpdate (tuple=0x28ccbb40, curcid=13, 
> buffer=756) at tqual.c:620

Well, this apparently indicates a bug in the new multixact code, but
there's not enough info here to figure out what went wrong.  Can you
create a test case that will let someone else reproduce the problem?

			regards, tom lane



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group