Postgres Pro
Downloads
Home   >   mailing lists

Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running - Mailing list pgsql-bugs

From Frank van Vugt
Subject Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running
Date
Msg-id 200412070013.44716.ftm.van.vugt@foxi.nl
Whole thread Raw
In response to Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tree view 
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.

pgsql-bugs by date:

Previous
From: "Ed L."
Date:
Subject: Re: serial drop error
Next
From: Tom Lane
Date:
Subject: Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running