Re: "invalid memory alloc request size <n>" in deferred trigger causes transaction to fail, but the backend keeps running

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: "invalid memory alloc request size <n>" in deferred trigger causes transaction to fail, but the backend keeps running
Date: 2004-12-03 01:35:53
Message-ID: 10980.1102037753@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl> writes:
> Ok, here are the results of the assertion TRAP (mind you, same error on the
> same line, but a different machine than the original)

That's another can't-happen problem. As best I can tell, this suggests
that the tuple descriptor associated with the RELOID catalog cache has
gotten clobbered (it should have the HASOID bit set, but an Assert that
says it does is failing).

Either you've found some code path that clobbers random bits of memory,
or you've got flaky hardware. But the same error on two different
machines makes the second theory a bit hard to swallow.

What's the hardware platform exactly? Is it 64-bit, or anything at all
off the beaten path?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Stephan Szabo 2004-12-03 04:32:43 Re: Foreign keys referencing parent table fails on insert
Previous Message Frank van Vugt 2004-12-03 01:26:50 Re: "invalid memory alloc request size <n>" in deferred trigger causes transaction to fail, but the backend keeps running