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

From: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-06 23:13:44
Message-ID: 200412070013.44716.ftm.van.vugt@foxi.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Tom,

> Looks like the problem is associated with DEFERRED AFTER triggers

> The attached patch fixes the test case you sent; can you
> try it against your other problem?

I patched RC1 with this and tried the conversion again. Though still running,
it's passed the point where the mem-alloc error occured earlier, so it would
seem we're in the clear on this one.

Thanks for the quick fix !

I guess this patch is already in the RC2 tree?

--
Best,

Frank.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2004-12-06 23:20:51 Re: "invalid memory alloc request size <n>" in deferred trigger causes transaction to fail, but the backend keeps running
Previous Message Belbin, Peter 2004-12-06 22:43:26 solaris 10 with gcc 3.3.2