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: 2005-10-27 13:40:02
Message-ID: 18237.1130420402@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matteo Beccati 2005-10-27 13:45:16 Re: ERROR: invalid memory alloc request size <a_big_number_here>
Previous Message Tom Lane 2005-10-27 13:35:54 Re: ERROR: invalid memory alloc request size <a_big_number_here>