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 21711.1102089054@sss.pgh.pa.us
Whole thread Raw
In response to 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>)
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:
>> This is the expected case.  The failure in CopySnapshot has got to
>> indicate that somebody set one or the other field to some bizarrely
>> large value, though.  I take it you didn't run the watchpointed backend
>> far enough to get the memory-alloc error?

> Oh, but I did.....

[ scratches head ... ]  AFAICS, the CopySnapshot that gets the error
must be trying to copy one or the other of those snapshots.  Maybe you
should look at the address passed to CopySnapshot and see what it's
really pointing at, and where it came from.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Frank van Vugt
Date:
Subject: Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running
Next
From: postgresbugs
Date:
Subject: Re: Foreign keys referencing parent table fails on insert