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

> Obviously, since the backend keeps running, it won't be easy to get my hands
> on the backtrace from when this error occurs and I'm wondering about the best
> way to proceed in order to produce some helpfull input to the developers.

Provide a reproducible test case maybe?

Also, building with --enable-cassert might help track it down.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Frank van Vugt
Date:
Subject: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running
Next
From: Tom Lane
Date:
Subject: Re: Column names: where, group by, having inconsistent behaviour?