Quick Links

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:02:15
Message-ID:	10609.1102035735@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:
>> Does anything happen before the SAVEPOINT?

> Actually, the SQL involved is v7.4.6,

Not with that backtrace, it isn't.

regards, tom lane

In response to

Re: "invalid memory alloc request size <n>" in deferred trigger causes transaction to fail, but the backend keeps running at 2004-12-03 00:50:35 from Frank van Vugt

Responses

Re: "invalid memory alloc request size <n>" in deferred trigger causes transaction to fail, but the backend keeps running at 2004-12-03 01:10:09 from Frank van Vugt

Browse pgsql-bugs by date

	From	Date	Subject
Next Message	Frank van Vugt	2004-12-03 01:10:09	Re: "invalid memory alloc request size <n>" in deferred trigger causes transaction to fail, but the backend keeps running
Previous Message	Tom Lane	2004-12-03 00:59:31	Re: "invalid memory alloc request size <n>" in deferred trigger causes transaction to fail, but the backend keeps running