Matteo Beccati <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
